Non-persistable entity expose throught OData 4 in v10.24.1

0
Hi all,  We have been using studio 10.15 for since release and we wanted to upgrade the apps so we did on the 2 days ago to 10.24.1 We are now having an error when creating a non-persistable entity (no commit not refresh in client), in a microflow, that is exposed via OData (because it's a parameter of an exposed microflow) to call the exposed method: 'Entity UserManagement.EntUMRegisterAccountRequestBody is not remote'   Is anyone else having to deal with this? What does 'is not remote' mean?   Here's the last bit of stacktrace: Advanced stacktrace: at com.mendix.modules.microflowengine.MicroflowUtil$.processException(MicroflowUtil.scala:73) Caused by: java.lang.IllegalArgumentException: Entity UserManagement.EntUMRegisterAccountRequestBody is not remote at com.mendix.connectionbus.handler.RemoteKeyMappingImpl$Retriever.getTableInfo(RemoteKeyMappingImpl.scala:267) at com.mendix.connectionbus.handler.RemoteKeyMappingImpl$Retriever.$init$(RemoteKeyMappingImpl.scala:259) at com.mendix.connectionbus.handler.RemoteKeyMappingImpl$IdRetriever.<init>(RemoteKeyMappingImpl.scala:45) at com.mendix.connectionbus.handler.RemoteKeyMappingImpl.getMendixIdFromPKs(RemoteKeyMappingImpl.scala:41) at com.mendix.modules.microflowengine.actions.mxobject.MappedMxIdentifierResolver.$anonfun$resolveMxIdentifier$1(MappedMxIdentifierResolver.scala:20) at scala.Option.flatMap(Option.scala:283)  
asked
5 answers
0

I’m experiencing the same issue.Previously, I was using version 10.18.4, but after upgrading to version 10.24.2, I’m getting a message saying that the non-persistent entity "is not remote."Have you found a solution to this issue?

answered
0

Hello everyone,

Adding my experience here as I'm facing the exact same problem.

I'm working on a fresh project built with Mendix Studio Pro 10.24.2. Just like others have reported, exposing a Non-Persistent Entity through a published OData v4 service results in the "is not remote" error. The setup is very straightforward, with no complex logic involved.

Given that this seems to be happening on recent Mendix versions, I wanted to check if anyone has managed to find a solution or a viable workaround. Any help would be greatly appreciated.

Thank you.

answered
0

This sounds like a bug. I believe there is a new version 10.24.5 which does fix something like this: 

  • We fixed an issue in external OData entity's object initialization where specifying the value for a key via a microflow expression failed.

 

Maybe try that? 

answered
0

The issue is definitely a bug in the standard "Create Object" microflow activity when dealing with an NPE for a Consumed OData service in Mendix 10.24.x.

The workaround is to create a custom Java Action that instantiates the object directly. A simple Java Action that takes the entity name as a String parameter and uses Core.instantiate(getContext(), entityName) in its body works perfectly.

By replacing the "Create Object" activity with a call to this Java Action, we completely bypassed the bug. Hope this helps!

answered
0

It seems that when you assign a value to an 'Attribute' while performing 'Create Object', an 'is not remote' error occurs. We solved this problem by using 'Create Object' and 'Change Object' separately.

 

스크린샷 2025-09-12 132558.png

answered