NoSQL data often comes with random items per Bundle. This is a repeating pain when setting up modules because system shows always only Bundle Order Position 1 while we SHOULD be able to choose to expose the Position(s) which DO include the data and documents we actually need. Often in datasets the first items are test items carrying incomplete set of items. Without being able to see and connect the (real) desired items (later positions) the further module setup becomes impossible.
Using a filter to force only desired Bundle Order Position to pass through won’t help because even after filtering the following models do see only the Position 1.
This should be fixed so that user can easily change the Position (content to be reflected and displayed on further modules) and system will reflect the content accordingly.
For example results from Google Firestore (fields) can contain just few items or lot of items depending on actual data. This is by design and accepted. Some use cases for example work so that the data withing a single Bundle accumulates to NoSQL database only over the time. The fix should be the Make UI improvement, not the modification of data assets.
SQL databases have always defined structure. NoSQL only after the data has been added.
