09-03-2019, 07:04 PM
Hi WhenInSpace,
We typically see each project as its own app. When you export a toolkit from LCM, you receive a config file that points to the project it was exported from. Calling APIs will reference the project the config points to.
With that being said, there are special cases for having an app that can access multiple projects. Is there a reason why your app needs to access multiple projects? Although its possible to do, all the APIs do not fully support this yet and there are some things you need to consider. If you'd like, you can send us an email so we can get a better understanding of what you app does. From there we can talk about potential workarounds and possible updates to APIs as needed.
- Efrain
We typically see each project as its own app. When you export a toolkit from LCM, you receive a config file that points to the project it was exported from. Calling APIs will reference the project the config points to.
With that being said, there are special cases for having an app that can access multiple projects. Is there a reason why your app needs to access multiple projects? Although its possible to do, all the APIs do not fully support this yet and there are some things you need to consider. If you'd like, you can send us an email so we can get a better understanding of what you app does. From there we can talk about potential workarounds and possible updates to APIs as needed.
- Efrain