Skip to main content
Solved

Problem recreating a Customized field in Astea 15.2

  • April 8, 2022
  • 1 reply
  • 58 views
bskallerud
Sidekick (Customer)
Forum|alt.badge.img+11

Migrating from 12.5 to 15.2, I have had to recreate some customized fields in v15.2 (customizations made with customizer does not upgrade). This has been easy enough - just create a “new” customized field in 15.2, in the correct module, with the same name and data type as in 12.5, and all data is shown correctly.

I now try to add this field: 

But get the following error when I try to save or publish: 

I have already added this field to one of our profiles, but for this one it will not work. Data type is correct. I can not add a field of type Object. I have tried to rename the column in the database

I rather not create the the field with a slightly different name, as I want to have customizations consistent across our different profiles (we do quite a bit of PowerBI-reports direct from SQL).

I have also checked out the possibility of copying the customizations from one profile to the other, but this will most probably create some issues with data already in the profile (for drop-down boxes, all lines must be added manually in the customizer even if the data is already in the database - and there are a few lines) 

 

Best answer by Phil Seifert

Hi Bjørn,

I recall a few months ago another customer had problems adding a field where the Customizer complained it already existed, etc.  It was in v15.3.

It may not be exactly the same situation but can you take a look at the steps I provided for that customer at the end of this topic:

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

What I am thinking is that after you removed the field, you did not publish to all and then tried adding the field where you needed.  Otherwise, we are probably going to have to look at this together.

 

View original

Phil Seifert
Ultimate Hero (Employee)
Forum|alt.badge.img+23
  • Phil Seifert
  • Ultimate Hero (Employee)
  • April 9, 2022

Hi Bjørn,

I recall a few months ago another customer had problems adding a field where the Customizer complained it already existed, etc.  It was in v15.3.

It may not be exactly the same situation but can you take a look at the steps I provided for that customer at the end of this topic:

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

What I am thinking is that after you removed the field, you did not publish to all and then tried adding the field where you needed.  Otherwise, we are probably going to have to look at this together.

 

Please mark any comments which answered your question as Best Answer so the topic is easier recognised as answered and closed.

Reply


Terms & ConditionsCookie settings

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