Introduction


Using the Cloud Collection CMS front end you can create Live Feed (Remote Data Source) or SQL DB (Local Data Source)


When you create a SQL DB from a Cloud Collection Data Source and add a column that contains an asset such as an image or media file you can define that asset as in a local file or on the Internet.


The benefit of storing large asset on the internet are:

  • Reduces the size of the app to be downloaded, as assets like video are stored on the cloud not in the app on the device.
  • Easier to change the asset as it's done directly on the cloud
  • Speed up App Generation: When an app is generated all the files of the app are moved between multiple cloud servers. If the app contains the heavy assets it can take much much longer to generate the app. Most if that time is used to move large assets between different servers. 
    • Critically: You can change the location of your asset on the fly. If your goal is to create app with all asset stored locally. Develop with asset stored on the internet, then switch to local storage when you are ready to publish your app.



Local file storage, On the Internet Storage


When your SQL DB is generated from a Cloud Collection you can use the setting of that Cloud Collection to decide where the assets will be stored.

Note that this setting is valid SOLELY for SQL DB (Local Data Source).
For Live Feeds (Remote Datasource) all assets are always stored in the Cloud.



Select the Collection driving the SQL DB.

In our example the Collection is named 'My Local and Remote data'


 


Then click on "Edit Columns".


When an Asset type is on of the following (circled in red):

 

 


You have the opportunity to decide where the matching asset will be stored:




The "Attachments for Local Data Source" column will let you know if your asset is "In a Local File" or "On the Internet".



To change the asset setting click on "Edit".


You can now use the drop-down to define your asset as local or remote on the fly.