Hi,
We are migrating from O11 to ODC. After doing the necessary changes and fixing any errors that came along with the migration, I was publishing the application when at around 70% of the progress of publishing, this error occurred as shown in the image.
I am unaware why this happened as when I checked whether the made changes are getting saved by opening another instance of the same app inside another tab in ODC Studio, it is getting saved. But, due to it being not published properly, it may not be getting saved with a new version in the cloud - this is my opinion why I am not able to open any of the screens defined in that app in the browser.
Please help!
Thanks.
That error is u documented. Please use the feedback button in ODC Studio, and after that create a support case.
Regards,
Daniel
Thanks for helping.
Hi Shubham,
we have encountered this issue in the past and it was caused by the following pattern.
The problematic pattern arises when using inner expressions in conjunction with the inline type mapping feature, especially when attempting to utilize variables of different types as input parameters. To address this issue, we recommend avoiding the combination of expressions and inline mappings.So look over your mappings (for example: append, appendAll, ...) and ensure your mappings are not doing any data type conversions
Thank you. I'll check it at my end.
You marked the reply as solution, but you also said you will check it. So is this the solution or you still have to check it is?
By mistakenly I marked it as a solution. Thanks for noticing it and letting me know. The app we are working on is vast in terms of logic and there are a lot of factors that we have introduced in it, such as, role-based visibility of content and role-based access to certain elements. And in ODC, we are yet to decide the roles and there are a lot of other transformations that'll be implemented. That'll make it difficult to tell what is the exact issue that is causing the error. We have raised a support ticket through our company's dev environment; maybe, they can find the solution. I'll update it here.