Hello, I'm facing an issue where my server action ouput structure data is different between producer module and consumer module.To make it eve more odd there's another consumer module where everthing is fine withou any discrepancies but the new consumer module is getting only some data and not all.For context the consumer module where everthing is fine is a reactive module while the consumer module where we have the issue it's a mobile module.Thanks in advance,Pedro Mascarenhas
It was a bug debug in Service Studio it seems, after adding a JSON on a log I'm seeing the expected output structure.
Hello,
It’s possible that the Reactive module has already picked up the latest updates from the producer, while the Mobile module hasn’t.
In the Mobile module, press CTRL + Q to open Dependencies, then click Refresh. You should see a retry/refresh icon next to the producer module in the popup. After refreshing, the missing attributes should appear.
That's not the case, everything is refreshed.
@Pedro Mascarenhas : Can you remove all the reference and re-add it and see if it makes a difference ? Also do you mind sharing some screenshot of the structure on how it see in both producer and consumer ?
Both the web and mobile modules use the producer module. It's unlikely there will be any difference in results from a server action of the producer module.
I also think like Sherif, you should check your dependencies, it might not have been refreshed yet.
In fact, there are some changes that won't raise the need of refreshing dependencies. But we still need to republish the consumer to let new dll compiled to the consumer module.
Hope this help
Hello Pedro,
This behavior usually points to a consumer-side metadata mismatch, rather than a runtime data issue.
A few things to check:
Refresh the dependency in the Mobile module (Manage Dependencies → republish the reference). If the output structure changed in the producer at any point, the Mobile module may still be holding an older contract.
Compare the structure definition in both consumers. Even if the action is the same, attributes can be missing, optional, or out of order due to an outdated reference.
Check for serialization limitations in the Mobile module, especially if the structure includes complex types (lists within lists, nullable attributes, or records with unsupported data types).
Ensure the producer module was republished after the last structure change, and that the Mobile app was rebuilt.
As a last resort, remove and re-add the producer reference in the affected Mobile module.
The fact that Reactive works fine strongly suggests a stale or partially updated dependency in the Mobile consumer.
Hope this helps.