If I follow you correctly, your model contains a Display/Simple Table (call this element C) which contains a repetitive Data Types/Database Record (call this repetitive element D, and note that it can also be a Data Types/Data Structure element), as in the following screenshot:
One alternative would be to replace the simple table with a new Data Types/Data Structure (C) which would contain repetitive structure D, as in the following screenshot:
Another alternative would be to use a chooser directly (replacing its default <Value> and <Options>) as in the following screenshot:
A thought regarding your usage of code tables provided in CSV format: As I understand your description it seems you are constantly reading and parsing the text files (every time a relevant chooser is populated?), and that would certainly prove to be a performance hit. The only reason to implement that way, is in case these files change constantly, otherwise it makes sense to have a process which reads them, parses them and stores the data in database tables. This process can be run at varying intervals, such as:
Regards,
David
To use the full functionality of this web site, JavaScript needs to be turned on.
For best results, use the Firefox browser..
Copyright © 2003-2017 - Tersus Software Ltd., All rights reserved. Terms of Use License Graphic design by EmaraDesign