Skip to main content
Solved

Is there a way to totally remove a customization?


bskallerud
Sidekick (Customer)
Forum|alt.badge.img+11

I need to create a customization for a new profile, and it needs a specific name (as the field already exist in the database. I created the field, but managed to use the wrong datatype (text instead of drop-down), and when I try to create it again I of course get the message that an object with this name already exist. Is there a way to either remove the customization object or changes it’s properties? Or will I have to create a new profile?

Best answer by Phil Seifert

We seemed to have resolved this by removing all the customizer customisations.  After this, we found that there was still a cconth state query referencing this column in the /bin/customizations/ASTC/DAL/cconth_state.mssquerycache.

Because the field was still in the query, the Customizer application believed it could not add this column as it already existed.  We just removed the reference to the field in this file and now you were able to add the column as desired with a drop down.

View original

4 replies

Phil Seifert
Ultimate Hero (Employee)
Forum|alt.badge.img+24
  • Ultimate Hero (Employee)
  • 1322 replies
  • January 9, 2022

Hi Bjørn,

If I understand your problem correctly, you have a field you added with the wrong definition and now cannot create the same field again with the correct definition.

This is similar to an earlier IFS Community post I provided a solution to do this for another customer.  Perhaps you should review the steps posted in this topic at the end to do this via the Customizer UI and see if you can fix your issue.

https://community.ifs.com/alliance-265/how-to-change-added-field-in-customizer-v15-3-16335

Pay attention that you need to save and publish the changes once you delete the field or it will be picked up as already existing.


bskallerud
Sidekick (Customer)
Forum|alt.badge.img+11
  • Author
  • Sidekick (Customer)
  • 207 replies
  • January 9, 2022

Hi Phil,

I tested, but still get

 


Phil Seifert
Ultimate Hero (Employee)
Forum|alt.badge.img+24
  • Ultimate Hero (Employee)
  • 1322 replies
  • January 9, 2022

You are sure you deleted the field first, saved and then published to all before logging out, in and adding the field again!?  This is how it was fixed for the other user. 


Phil Seifert
Ultimate Hero (Employee)
Forum|alt.badge.img+24
  • Ultimate Hero (Employee)
  • 1322 replies
  • Answer
  • January 9, 2022

We seemed to have resolved this by removing all the customizer customisations.  After this, we found that there was still a cconth state query referencing this column in the /bin/customizations/ASTC/DAL/cconth_state.mssquerycache.

Because the field was still in the query, the Customizer application believed it could not add this column as it already existed.  We just removed the reference to the field in this file and now you were able to add the column as desired with a drop down.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings