About collection definitions
When portal content calls for a collection by name, the Collection Definitions table is first consulted to determine the data source from which to fetch the collection. If an entry is not found, the default data source is queried. If the default data source does not contain the collection, an error occurs.
Restrictions
When setting up a multiplexed collection, be aware that the system allows you to use only properties that exist in each of the underlying data sources with the same name and data type. Any properties that do not meet these conditions are not available for use.
Collection definition caching
The first time a collection is loaded, the underlying data source is queried to determine the properties available in the collection. This information is then cached and used repeatedly for performance.
If you change the collection definition during development, you must clear the portal cache to force the system to re-query. This can be done in the Portal Manager using the button.
In the case of Mongoose-based (back office) data sources, such as the Infor SyteLine data source, Mongoose also caches the collection definition itself. You must clear the Mongoose cache prior to clearing the portal cache. For on-premises environments, this can be done in the Portal Manager using the button. For cloud environments, you must contact the Infor Cloud team to have the IDO cache cleared.
In the case of a multiplexed data source collection, the collection definition is actually a union of multiple collections. As mentioned, there must be a matching property in all of the underlying collection definitions for the multiplexed collection definition to support it. Therefore, if you add a property to a Mongoose IDO, make sure that it is added to all of the Mongoose data sources underlying the multiplex. Also, make sure that you discard the IDO cache in each data source prior to clearing the portal cache, so the new property can be found in all of them.