Skip to main content
Solved

Cannot Read Properties of null after crud action

  • April 16, 2026
  • 4 replies
  • 47 views

KennethP
Sidekick (Customer)
Forum|alt.badge.img+5

We are experiencing a strange client error after our upgrade to 25R2. A client error “cannot read properties of null” appears after saving a record in a list or assistant. The save operation finishes, though. But in an assistant the client error still blocks the flow because the page has to be reloaded or abandoned. Reading the failing code in the console in developer tools, it seems to be related to reading the home pages for entities, constructing URLs for those. It only appears for certain permission sets though, but we cannot figure out exactly what is missing. Any clues?

Best answer by AveTonitM

Yes, we got the case reference CS0509507.

When looking at SU5 release notes I suspect the fix reference is CS0474389 (with lowest priority). One can argue what the priority should be, because the users are quite frustrated when client errors occur after every save action.

4 replies

KennethP
Sidekick (Customer)
Forum|alt.badge.img+5
  • Author
  • Sidekick (Customer)
  • April 22, 2026

Update: a debug session shows that when we get the error, there is no entry for null in an array of “home page for entity” information (this is in JavaScript code in some part of the client framework. But when we don’t get the error there is an entry there: TravelRequestManager.

Granting TravelRequestManagerHandling to the user (through a permission set) fixes the problem!

But why? We have not been able to reproduce this by simply removing that projection from a full role, or constructing a small one with only access to one page. The only special thing about TravelRequestManager that I can see is that it is the page that is not home for an entity with the lowest number in the navigator. 

Clearly this has to be a framework bug, but we cannot reproduce it clearly and we don’t know if it has already been fixed in a later version of the framework. 

 

Application service update: 25.2.3

Framework service update: 25.2.4

IFS Cloud Web version: 25.2.4.20260305184234.0

IFS Client Services version: 25.2.4.20260305184228.0

IFS Client Notification version: 25.2.4.20260305183143.0

IFS Chat version:

IFS OData provider version: 25.2.4.20260305065217.0


AveTonitM
Hero (Partner)
Forum|alt.badge.img+11
  • Hero (Partner)
  • April 22, 2026

We faces similar errors after upgrade to 25R2 SU3 among others in the “Supplier for Purchase Part” view. The client error is reproducable with end user permisison sets, but not as administrator user (IFSAPP). We didn’t find a way to fixing this as we don’t know what projection grant is missing.

We reported a support case to IFS and IFS support replied that this would be a “known product defect” and there would be a fix in 25R2 SU 5. So now we plan another upgrade.


KennethP
Sidekick (Customer)
Forum|alt.badge.img+5
  • Author
  • Sidekick (Customer)
  • April 22, 2026

Thanks ​@AveTonitM. There is always another upgrade to make 😊. We also got this in several places. But at it’s reassuring that it was already known and will be fixed. Will see if we can get support to confirm that in some way. You did not happen to get an issue number or so from them?

 


AveTonitM
Hero (Partner)
Forum|alt.badge.img+11
  • Hero (Partner)
  • Answer
  • April 22, 2026

Yes, we got the case reference CS0509507.

When looking at SU5 release notes I suspect the fix reference is CS0474389 (with lowest priority). One can argue what the priority should be, because the users are quite frustrated when client errors occur after every save action.