Can I populate an acronym list that varies by user

We have different offices that want different acronyms to show up on our log key.   There are over 30 acronyms that I currently have hard coded into the log key as text entities. Can I build an acronym list from a Lookup table maybe, so the user can select certain acronym list groups, depending on their needs?  I want them to be alphabetical, so it is hard to just tack onto the end.  I don't want to make 5 different versions of the log key template.

  • Szang - thank you again for your design and clear instructions.  I just completed this for my intent and it worked perfectly.

  • I realize this is after the fact but an alternative way to accomplish this is as follows:

    I created a data table in the library similar to above but instead of having Boleen fields for each office I set up a single user field as shown below.  In the user field I have entered the office/username of each user that wants each definition separated by commas:

    IN this case each user/office is represented by a single letter but they can be any unique text string such as "Paul at western regional office"

    The text entity that creates the legend listing is similar to what was used above except the text property is simplified to what is shown below

    The definition entity is similar.

    This has the following advantages:

    1. You can have an unlimited number of users/offices each with their own legend and you do not have to modify the data table to add a field for that user.  You also do not need to modify the report design to add a case to the text entity for the new user.

    2. It is simpler and less likely to generate errors.

    The disadvantage of this set up is that maintaining the library table becomes a bit hard as you have to enter each unique office/user name the exact same throughout the table and you cannot sort on a single office. Note that the comma separators are not required but make it easier to understand.

    Note in both alternates the selected user must match exactly the user name used in either the case statement or the user field of the data table.

    Just an alternative way of doing it that might appeal to others that have a lot of users each with their own specific desires.

    I have tested this and the results for both were Identical.  You would have to modify to use your data structure set up and table/field names.