Data lookup tables incorrectly setup - how best to correct?

Sam Ogden
Tera Guru

Hi All,

I've recently watched the video on the learning portal for the new licence model that is in place for Madrid release onwards.  With this now having a licence limit on the number of custom tables, I've started the process before we look to upgrade to get a grasp on how our instance is looking.

As part of this I've noticed we have several custom tables that are used for data lookup that have not been created extending the 'dl_matcher' table.  From what I understand data lookup tables will be exempt from the licence implications, but these are detected by being extended from 'dl_matcher'.

I wanted to know the best practice method to get our data lookups setup correctly to make sure we are not taking up licences where they are not needed.

We have a subcategory lookup table with a reference field on our incident table to this table.

All I can think is we will need to create a new subcategory lookup table being correctly extended from 'dl_matcher' table.  Populate this with the same data.  Create a new subcategory field on the incident table.  Run a fix script to copy the correct subcategory to the new field, then I can delete the old field and old lookup table.

Is there an easier/simpler method that won't involve me creating a new field/table?

Thanks

Sam

1 ACCEPTED SOLUTION

We have a lot of data but you don't need to use every field in every definition.

Here is screen shot of our lookup record:

find_real_file.png

 

and the lookup definitions:

find_real_file.png

View solution in original post

5 REPLIES 5

We have a lot of data but you don't need to use every field in every definition.

Here is screen shot of our lookup record:

find_real_file.png

 

and the lookup definitions:

find_real_file.png