Forum Discussion
Solved
Which best choice: Flow to get data from Lookup Column or Additional Column from Lookup Column?
If I have some List like: - 1.1 Country: Country ID, Country Name - 1.2 Purpose: Purpose ID, Purpose Name - 2. Product: Product ID, Product Name, Country ID, Country Name, Purpose ID, Purpose Name...
- OK, if different permissions apply for each stage separate lists makes sense. Also your choice for not using Managed Metadata Term Sets makes sense if additional data needs to be stored for each item.
Changing a List Item's content type won't cause loosing your data if your content types share the same Site Columns.
Modeling a relational data model in SharePoint this way is certainly possible to some end, but comes with challenges as you're experiencing at first hand now. In the end you might be better off modeling your data in a traditional relational database system (Azure SQL DB for example) and exposing it in SharePoint as an app. A PowerApp might work or a Provider-hosted add-in would provide the most flexibility...
paulpascha I never try this approach before. But if I change the content Type of Item, does the content belongs to the previous content type lost?
And I need Lists to have difference Permission.
I also think you should consider storing your data for Country, Purpose and maybe even Product in a Managed Metadata Term Set instead of SharePoint Lists.
Yes, I considered to store that data in Managed Metadata Term Set, but I need some column which belongs to this data too, like:
Country: Country ID, Language, Nationality, Capital...
Purpose: Purpose ID
Product: Country ID, Purpose ID (Product ID = Country ID + Purpose ID)
OK, if different permissions apply for each stage separate lists makes sense. Also your choice for not using Managed Metadata Term Sets makes sense if additional data needs to be stored for each item.
Changing a List Item's content type won't cause loosing your data if your content types share the same Site Columns.
Modeling a relational data model in SharePoint this way is certainly possible to some end, but comes with challenges as you're experiencing at first hand now. In the end you might be better off modeling your data in a traditional relational database system (Azure SQL DB for example) and exposing it in SharePoint as an app. A PowerApp might work or a Provider-hosted add-in would provide the most flexibility...
Changing a List Item's content type won't cause loosing your data if your content types share the same Site Columns.
Modeling a relational data model in SharePoint this way is certainly possible to some end, but comes with challenges as you're experiencing at first hand now. In the end you might be better off modeling your data in a traditional relational database system (Azure SQL DB for example) and exposing it in SharePoint as an app. A PowerApp might work or a Provider-hosted add-in would provide the most flexibility...
I am very eager to see the combination of SharePoint and SQL, which may be the best method for this case. But now I only have time to focus on SharePoint.
Thanks for your help in all these days. Glad to know you.