In the previous post we covered how to track changes to application files in an update set so they can be moved between instance environments. Sometimes, especially when you are building a vendor application that will be distributed to multiple customers, you might want the option to provide initial data or demo data without defining them as application files to be tracked in update sets once they are deployed.
Selective application files can be created from any table in your application. Individual records saved as application files will be included with your application. As opposed to application file tables that are always deployed with your app, and always tracked in update sets, these records can be defined to install only on initial install or even make them optionally installed.
Any data in your application that resides on tables that do not extend Application File table will not usually be shipped with your application. If you want to provide selectable data from these tables so they are available in other instances or to customers through the marketplace, you need to manually create application files for the records.
From the list of records, select the rows you want to include in your app and select the Create Application File option from the list choice actions. You'll notice that you have options on when the records will be loaded.
- New Install - records will be loaded only on the initial install of the application. If there are changes to the record in a future release, existing instances will not receive the changes.
- New Install and Upgrades - records installed on initial and all future application upgrades.
- New Install with Demo Data - when installing an application that has records marked as demo data there will be an option to install the data on the initial installation only.