Skip to main content

We are currently on Apps10 UPD13 but have noticed this issue since going live on Apps 10.  On occasion, a previously visible custom field (as configured in their base profile) will no longer be visible for a user.  The user discovers the issue when using a saved search (link on a start page) that references the custom field.  They will get an error message referencing the field name when they click the link.  Here is an example:

 

We have found two ways to correct the issue.  One method is for an administrator to delete the branch for the impacted screen from the user’s personal profile – when the user logs back in the field is visible and the saved search works.  The other method is to have the user re-add the field manually to their layout (e.g., via column chooser).  The symptoms and resolutions suggest that something is happening to the user’s personal profile that makes the field no longer visible.  The issue happens intermittently and inconsistently – not always to users that share the same base profile nor always for the same screen in IFS.  It happens often enough to be a pain, but not consistently enough for us to know the root cause.  Has anyone else experienced this issue and found a way to prevent it from happening?

 

Thanks!

Yes, it happens fairly often, but inconsistently to us in Version 9 as well.  It typically has to do with updating something on that related view, or deploying another database change, but we’ve not correlated the change to the user themselves or their personal profile.  We see it after our maintenance period most often and usually after we’ve deployed some database change - but often in an area unrelated to where they’ve lost the custom field.  But we’ve never isolated the exact cause in a predictable or preventative way.  We only know when it happens AFTER it happens and the helpdesk calls start.

It is annoying to be sure, but also after 7+ years, we live with it.  Our solution is always the latter one, just tell the user to reselect via column chooser.

Hi, 

We had the same issue on IFS App9. I found out that the reason is “re-compilation” of LU-packages.

The issue occured when I added CustomFields to LU “CustomerOrderLine” or  “PurchaseOrderLine” and did “Syncronize”. Not all LUs cause the problem, but some.

I’ve reported it and got answare that “The issue will be fixed by patch 149850”.

I suggest you report the same issue on your version of IFS.

Br. Barbara

Reply


Terms & ConditionsCookie settings