I have one Particle account and three products.The three products match different hardware configurations each of which runs its own app. All of the products use common integrations that are defined at the account level. There are no integrations defined at the product level. One of my products is approaching the upper limits of the Sandbox for Data Operations and Cellular Data. When I upgrade to Growth for this product must I touch my integrations?
Maybe. We recommend using product-level integrations wherever possible.
However, if you have claimed all devices to a single account and are using integrations in that account, you can continue to do so after migrating to growth (or enterprise).
Thanks. Can they exist in both locations with the same name? If yes and if I clone the integrations so that they exist in both locations is there a runtime resolution hierarchy on the server side?
You can have the integration in both the product and the claimed owner account with the same event name, however beware as the integration will trigger twice.
We recommend using product integrations for several reasons:
- It keeps all of the stuff with the product
- It allows the use of unclaimed product devices, which will simplify your device onboarding process
- It allows firmware developers to claim product devices to their own account, which makes it easy to flash firmware directly from Particle Workbench, Web IDE, or CLI.
Quick update: I copied the integration to the product and disabled the same integration in the sandbox. It worked perfectly. No data loss. For webhook users, note that there are additional json objects in the data coming in to the integration when moved from the sandbox to the product. These are: “userid”: , “version”:, “public”:, and “productID”: .
2 Likes