Hi All,
Unfortunately, I have some junk basic data values, already used, which prevents me from cleaning and deleting.
Can I hide these values in order not to appear in LoV and not to be used anymore?
Many Thanks in advance
Abdeslam
Hi All,
Unfortunately, I have some junk basic data values, already used, which prevents me from cleaning and deleting.
Can I hide these values in order not to appear in LoV and not to be used anymore?
Many Thanks in advance
Abdeslam
Best answer by martin.surasky
Hi
I think the answer here is “IT DEPENDS”. Let me drill down a bit.
Sometimes you can retire or hide “junk” basic data values rather than delete them, and that is usually the safer approach when they are already referenced. SOMETIMES doesn’t mean ALWAYS... not even USUALLY.
The exact mechanism depends on what kind of basic data the values are (Code String values? Custom lookup/Enumeration? Control Types? User-defined basic data in a specific module?). The patterns below are common in IFS:
Preferred options (in order):
Many IFS basic-data entities have a status-style control such as:
If the value can be marked inactive:
This is the cleanest solution.
Some code tables support:
Set a Valid To in the past (or end-date it going forward).
If YOU control the process of Basic Data creation (Custom Entity or Custom Field) you may be able to prevent it from appearing in LoVs by adjusting:
This many times is the only option available and what most people do. Examples:
This protects against accidental use even if it doesn’t help with hiding it.
Do you know precisely what associations prevent your LOV values from being physically removed? Are those related records part of hour transaction history that you don’t want to remove or you simply don’t know how to remove them as well?
Thanks
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.