LOCAL REFERENCE FIELDS

I am currently working in a T24 implementation where the CUSTOMER application has 100 local reference fields. I have never seen so many local reference fields. Is this normal? What are the disadvantages?

Hi Darcy,



We have more than 160 local reference fields in our CUSTOMER file.

The only disadvantage is the performance. This will bring down the performance of all the jQL statements.



My advice is to create a seperate local file and keep all your local reference fields in that file. And create a new VERSION for CUSTOMER file to update the local file.


_________

Hi,



I hope creating a new local table will not be a great solution from the business users side, because they cannot see the local reference fields in any of the CUSTOMER version.



Though from technical point of view, keeping a separate local development and a local reference field in CUSTOMER is same. It not same as far as the users are concerned.


Great power comes with great responsibilities.

I've found out there are some local reference fields in CUSTOMER which are not used anymore. Is there a procedure to remove them? If so please help me.



Thanks.

Hi,



Local reference fields once created cannot be removed, but you can change it to Not Used to indicate that those are no more in use.



In future, when you want to create a new local referecne fields, you can reuse the Not used field.


Regards,

Ramya

If you don?t have a smile, I will give you one of mine | www.smile.org.in

You can remove the local reference fields from Globus. Just that you will have to use a routine. It cannot be done directly at the application level. The routine should remove the link to the local ref from all the applications where it's been used and convert the data accordingly.



Finally, do not forget to take a backup before u venture into doing this.



Cheers,