0

Hi all,  In a previous post i've asked a question about organisation structures in my app, i've changed the way i've done it (hence a new post) and have come up against an issue. Rather than using enums to get all the different structures in i've used a data base and reference selectors. Here is the domain model.    What i want to do now is make it so when adding/editing CorePropertyInformation, you can select the Level 2 structure, depending on what you select, a new dropdown/reference selector will appear and give you all Level 3 options that are referenced to the Level 2 option you selected. Then same again, Level 4 will appear showing options referenced to the Level 3 you selected.  I originally had this set up so you link to to Level 4 and Level 2 & 3 auto populate, but the client would like to start at Level 2 and work down the tree, as some properties will only be linked to a Level 2. In the reference selector's "Selectable Object" option I can make it so in a level 3 selector it only shows the results from a certain Level 2 value, but doing it this way would mean i'd have to have a reference selector for every Level 3 and every Level 4, this is well over 100 and that is not practical. Is there anyway to limit what the user can pick in the Level 3 selector based on what they choose in level 2 and same again for level 4 based on level 3. I've wondered about a microflow but can't work out the right way to do it.  Or is there another way that anyone can suggest!  Many thanks! Garion   EDIT:  I've now got this.  However when I try to import my data using the Excel importer it does not add the reference.  I've add all Level 2 fields, then gone to add Level 3. Level 3 imports fine but does not reference level 3.  

asked 2018-07-30

2 answers