We are looking to create a ledger that links a particle e# to a string, and then use a logic function to lookup the e# and append the string to the data packet.
Follow up Questions:
Is there, or will there be a way to update a ledger via the cloud API?
Is there a reason I should use a product scoped ledger over a device scoped ledger? Is there a number of ledgers limit? My initial though would be a device level ledger might be a better option.
I'm not entirely sure I understand your use-case, but I think you will want a Cloud Ledger, device scoped.
In a Device to Cloud the value is set by the device, and in Cloud to Device, the value is sent from the cloud to the device, both of which would defeat the purpose of not storing an email on the device itself.
The scope determines whether each device has its own JSON object of data, or each product has. If each device is only associated with one email, that's an obvious choice. Making it product-scoped is usually only applicable for global settings that affect all devices.
Cloud ledger values can be set using the cloud API.
A more common solution would be to only store the customers email in your back-end service, so it wouldn't be on Particle's servers, either.
Yes your assumptions are correct, Cloud Ledger, and I think device scoped makes the most sense.
That’s great about the cloud api.
Yeah ideally the email would be managed entirely inhouse, but this is a temporary solution until a larger refactor can be implemented. Thanks for the help