Do newly created (non standard) attributes automatically get included in the ACS export?
when running out of standard attributes such as List or Text fields, it is possible to create them manually. I notice these do not get assigned API keys.
Can anyone confirm whether or not these attributes will be included in the ACS export for the object?
Yes, you can create flex/user-defined attributes from the Java client so long as you have Administrator privileges. When you create them, you define the name, API name and data type, and they are created under the class/subclass you were viewing when you clicked the “New” button. And yes, they do get APINames assigned when created, and these will be visible to ACS.
That said, ACS will include the new attribute if the tab the flex attribute was created in is selected in a filter being used by ACS. Note that the filter definition does not get down to which attributes are going to get processed, only which tabs will get processed. If an attribute is visible in a tab, it will get extracted by ACS when that filter is used. The only exception to this is LargeText attributes. Given what their size can be (up to 2GB), they can be enabled or disabled using the “Large text Options” pull-down list in the filter. This allows any visible LT attributes in a tab that will be processed by the filter to be included
