Custom fields are showing as mandatory after 24R2 upgrade
Hello,
we have done IFS cloud upgrade from 23R1 to 24R2 in use place environments and we noticed that after upgrading ,in the screen we are getting non mandatory custom fields shown as mandatory (please refer below snapshot) ,we have checked in page designer this fields are not set as required.
if we try to save it without entering value for that field ,still record is getting saved but it creates the confusion to user and we need to avoid that. please help if anyone has encountered this issue or any suggestions for the same.
Regards,
Gaurav
Page 1 / 1
@ACCGAURAP I’ve also recently upgraded a customer environment from 24R1 to 24R2 but I haven’t noticed such behaviour. Are your Page Configurations up to date? Meaning, have you rebased client configurations?
Hello @Marcel.Ausan ,we have rebased all the page configurations, and they are now in Up-to-date Baseline status . However, we are still encountering the issue.
@ACCGAURAP for another customer where we just upgraded to 24R2 we got into the same issue. Custom Fields show as mandatory. We’ve opened a support tikcet with IFS. We’ll wait to see what they say. I do believe it’s a bug.
This is interesting. Does this only apply to the fields created in the configuration layer?
@Marcel.Ausan, let us know what they suggest regarding this issue
@astfarazt , yes you understood it correctly, we are facing this issue only for the field created in the configuration layer.
@ACCGAURAP for another customer where we just upgraded to 24R2 we got into the same issue. Custom Fields show as mandatory. We’ve opened a support tikcet with IFS. We’ll wait to see what they say. I do believe it’s a bug.
@Marcel.Ausan Can you give us the IFS support ticket ID?
CS0333334 - @Marcel.Ausan @dasithdeelaka
We really need the “known issues” list of a release update would save quite some support tickets.
I have the same problem with a completely new installation 24.2.2, not just after the 24R2 upgrade. When I create a new custom field (attribute), it is shown as mandatory. As far as I know it is corrected in 24.2.3
Edited: The custom attribute is displayed as mandatory on the page, but we can save it with an empty value without any issues.
@AmyE - FYI for upcoming demos this month prior to our SU3 update next month.
Hi all
I just checked with @Tomasz Grzebula: This is an UI issue, which will not prevent you from saving the record itself, even if the custom fields were not populated. It has no further impact to the metadata of the entity “ActiveSeparate”. If you use the guided workflow via “New Service Request” (effectively generating a new Work Order), you will not face that issue.
Kind regards:
Marko
Hi all
I just checked with @Tomasz Grzebula: This is an UI issue, which will not prevent you from saving the record itself, even if the custom fields were not populated. It has no further impact to the metadata of the entity “ActiveSeparate”. If you use the guided workflow via “New Service Request” (effectively generating a new Work Order), you will not face that issue.
Kind regards:
Marko
It is fine that this will not stop the end user from proceeding, but it will still lead to the end users filling in a lot of “clutter” info to the fields that appear as mandatory, just to proceed. What is the plan from IFS’ side to solve this?
Br Hans
As far as I know it is corrected already and will be available in the newest Service Update 3. 24.2.3
Hi All,
The issue has already been addressed by the R&D and planned and fixed versions are given below.
We have checked the reported functionality with business opportunity window in 24R2 and observed the same issue. Earlier it was reported to R&D, and it was considered as a bug.
Additionally, after investigation, it appears the issue is only with the visual indication, the color of the field indicates it’s mandatory/required even if it’s not, but it’s still possible to proceed and save without supplying a value.
Can you please confirm with the customer whether they experience the same thing (fields showing as mandatory/required, but being able to ignore that indication and not submitting any value)? And I think you can ignore the value and still submit the data.
This bug has been resolved in versions (23.1.22 - 23R1 SU22, 23.2.15 - 23R2 SU15, 24.1.9 - 24R1 SU9, 24.2.3 - 24R2 SU3, 25.1E.0 - 25R1 EA)
Best Regards
Vishal Jaiswal
@Vishaljaiswal yes this bug is purely optical. We can save the records without filling any data in the custom fields.
We have already deployed 24.2.3 for the customer, and indeed the issue is resolved.
