Set the "Is External" property of the field to false. This property defines whether a field is included in any data communication outside of the component (external), database I/O is also considered 'external' communication (entity/occurrence parameters are also considered 'external' communication). This is the equivalent of not-in-database. Note that only modeled fields can be 'external' in the first place (an entity descriptor is needed which is generated from the modeled definitions); non-modeled fields (often called dummy fields) are by definition not external. Hope this help, Gerton

Hi Gerton, thank you for the fast reply. Am I right that even under u9, non-database fields (even if modeled and populated in the read trigger) are not passed to an entry or another component with the occurence or entity parameter, so the "Is External" will not  change the behaviour under U9?   TIA, Uli

sorry, my fault: occurrences or entities can not be parameters on entries. But will we have the same processing in U9 and U10 between components ? and will these fields be included with their values in the putlistitems/occ ? I will check against 10.2.02, but the important bit is what will happen in 10.3 TIA again, Uli