Hello,
I have implemented the Project Acelerator Tool of MS.
I have to add several new fields with the following behaviour:
First, the user selects a choice in the field Group. After that, the field Subgroup will show the records related to the Group.
Example: If the Group field selected is 2, the Subgroup field will show G,H,I and J.
I also have to import the data to the dataverse table but I'm not sure how to do it. Should their be new tables? The solution has already tables, as Projects, where I have to store the selections.
What is the best way to archive this?
Thanks in advance!
Hi @aorro93
I'm glad to hear it worked out 🙂
I would really appreciate it if you marked the solutions so others can also see that the topic is solved and what the solution was as well 🙏
Thank you so much! It was missing in the column lookup of the table Subgroup the data of the related Group. I've entered them manually and it's working perfectly.
Thanks
Thank you so much for your answer.
I'm trying the natively supported filtering as you recommended but I'm struggeling with some details.
I created the table group and subgroup. Group only contains the groups and subgroup contains every subgroup and another column with the group related.
After that, I've created the lookup columns:
1- In table project: lookup column to Group table
2- In table project: lookup column to Subgroup table
3- In table Subgroup: lookup column to Group table (I am not sure about this one)
Finally, I have added to the form the lookup columns Group and Subgroup (these two come from the table project) and Filtered the subgroup (in my real case in Subkind):
Could you guide me in the filtering? I amnot sure about how to get the wanted behaviour.
Thanks in advance!
My answer to the first question actually also applies to the second question. I would recommend using different tables for each group.
Natively filtering on option sets is not possible (although it can be done using this tool: Dependent Option Set Manager ~ CRM Answers)
But instead, I recommend using the natively supported filtering through relationships in lookup fields.
Example:
Lets say you have a project that is linked to Group 1 and you want to see only the relevant subgroups (A-F) based on this.
You need to establish the following relationships:
many to one between project and group (can be achieved by simple creating a lookup to group from the project table)
many to one between project and subgroup (can be achieved by simple creating a lookup to subgroup from the project table)
many to one between subgroup and group (can be achieved by simple creating a lookup to group from the subgroup table)
Then you first need to link each relevant subgroup to its main group.
After that you go to the subgroup lookup on form for the project and select "filtering". There you can select that it should apply the subgroup to group relationship as a filter. This will use the value from Group and only show you the relevant subgroups.
Doing it this way also ensures an easier way to keep track of the groups in the future as they now exist as data instead of choices. which is the way I personally prefer to handle list that either change dynamically over time or that I need to use for filtering.
WarrenBelz
146,552
Most Valuable Professional
RandyHayes
76,287
Super User 2024 Season 1
Pstork1
65,928
Most Valuable Professional