Is there a way to share lists between models? We use a number of different models all for the same company which uses the same structure - and it would be really handy if it were possible create a 'shared' master list(s) in one model that could be referenced by all the other models.
Solved! Go to Solution.
You can send lists from 1 model to another model, but i would strongly suggest that you consider building a Data Hub.
Please refer to the link below:
For your purpose, you can just look at item 2, i.e. "Import your data files into the data hub", but i would encourage you to read the entire document.
Thanks for the response, that's an interesting article.
My issue with this approach however is that using an import method I don't see how it's possible to delete items from the master list.
If you have any suggestions on this would be appreciated!
It is not possible to reference lists between the models, you have to import them to each model via actions.
A good way to export lists from a model (data hub model for example) is to first create a module (hierarchy management module), where you have line item for each list you are planning to export. Each line item is formated as the list you have in mind. Once that is done, you can create a view for each list and then create an action in other models to import from that view. It is a better way, because in views you can turn off the summary level (or top level), which is not possible when you import from the list directly. In this way, when import action is run, you will have all green checks, which gives a lot of comfort that all data is imported succesfullly.
Hope it helps,
The following is a technique to remove items now not included in the master list.
This assumes that the master list itself (or those included in the import) only contains the current items, and anything not included should be deleted in the target
Take the following example:
We have a product master module (probably in a hub)
P3 already existed in the target product list (now deleted from the master list) and let's assume we have already updated the Product list for the new "P6"
You will see there are two additional line items. 'Current?' is the flag we import from the Master module and 'Delete?' shows if that product is not included in the new master list
So, when we import the properties of the product via the import we use one of the import settings (not widely used)
This will remove the properties for P3 and toggle the delete flag to TRUE
You then set up a 'delete from list using selection' action using Delete? as the flag
Assuming you want all of this done automatically you should put the actions into a process:
1. Import to the list
2. Import the properties (as above)
3. Delete from list
You can always have 3 as a separate action if you want to manually check before running the delete.
This process is also useful for the Master lists itself. Ideally add a separate property in the source file/import
I hope this helps
@DavidSmith - the approach suggested works well if it's a small list.
In case its a huge list running in to number of 100k items then the availability and performance of the model will be impacted.