Hello,
I'm trying to deploy a new version of my application and I'm getting the following error:
My ODC Studio version is 1.4.8 / Build 6435.
Does anyone have a solution for this error?
Thank you,
Christian
There is no documentation for these error codes on the OutSystems website. It would be best to contact OutSystems support for a resolution.
Yesterday we have the same error on ODC. We just restart ODC and everything started to work normaly.
I dont know if this error is associated with the update of the ODC Studio to 1.4.9 or something like that, but our engeneering solution was: Restart ODC.
Hi everyone,
A workaround is:
1st - Download the last published version, and save it to your computer locally
2nd - Delete the application on ODC
3rd - Close and open the ODC studio (required to restart the ODC studio)
4th - Publish the version that was locally stored
@Gonçalo Cardoso this workaround is highly risky since this will delete the app from all the stages and all its data.
https://success.outsystems.com/documentation/outsystems_developer_cloud/deleting_apps_and_libraries/
Probé con esto y funcionó. Importante que el resto del equipo no haga ningún merge ni ningún publish del entorno. También cerrar el programa con todas las pestañas abiertas y empezar de nuevo.
Después pueden trabajar con normalidad sobre esa nueva versión publicada.
@Christian Labrada please open a support case so that we can follow up on that unexpected error.
Did anyone get a resolution to this issue.
We are facing it now. The workaround did not work, and our development is blocked.
We are now attempting to rebuild by copying and pasting into a new application.
I have lodged a ticket with support. In the meantime, seeing as we have recently started the project, I created a totally new application and copy/pasted everything over to the new application. Then wired up dependent applications to the new one.
However, this means we lose all our data. if this were in production, or if we had a whole lot of test data, our fix would not be possible.
I'll comment when I have a resolution. ODC is still awesome, it'll be good to get this one resolved though.
Soo... Our amazing front-end dev it looks like this is caused by a warning in the IDE causing a build error on the server
When the highlighted warning is removed, the build no longer fails:
We have also noticed on rare occasions an error won't immediately appear in the True Change list, but only when you click on the offending item. But most errors do work as expected. I suspect though that in this situation, the error would prevent starting a publish, so maybe not related.
Hope this helps! I'll comment when I get confirmation from OutSystems support.
Stuart
Feedback from OutSystems support.
Our issue was that ODC studio managed to remove an attribute from an assignment in a call to an action where it was mapping a structure to an entity. The Id attribute does not appear in ODC Studio, but the entity does have an Id. There is no warning or error displayed in the TrueChange list.
When published, the build fails because that attribute is not present.
OutSystems are working on a fix that I imagine will be in a new version of ODC Studio soon.
Our experience with ODC studio is to avoid as much as possible mapping structures in the call of actions.
It is preferable to have a local variable of the correct data type of the input of the action and do the mapping in an assign, as this avoids these errors while publishing.
--Tiago Bernardo
Tiago,
Thanks for your input. I'm not sure I entirely agree, but still I value your contribution.
Wouldn't we then have the same problem with mapping in an assign? It seems this is a bug in ODC Studio, rather than a poor coding practice.
Adding what is arguably a redundant local variable appears to be additional effort; although it is a small amount of extra effort.
The issue is not so much what coding practice we were using, but that the compilation messages in ODC Studio are not matching the compilation errors that occur on the server.
It turns out there were more than this particular compilation error that was causing issues. We had another issue recently, that was something else.
Kind regards,
After talking with Tiago at the conference, he explained that using an assign for mapping rather than directly in the call to the action is a workaround until the issue is resolved.
It turns out when the structure is changed, the mapping in the assign is not affected, whereas the mapping in the action call is.
It is a small amount of additional effort, but reduces your chances of having an error publishing an ODC application.
Thanks Tiago for working this out and explaining it to me!
Hi Tiago,
Today I have seen a few occasions where this error happens in an assign when the structure has been modified as well.
What seems to resolve it (aside from rebuilding the assign), is to disable the assign element and reenable it. This seems to refresh the structure in the assign.
I had the same error and this is my solution:
In one of my assign's for assigning to a structure i had an list within a list where i assigned entity data to a structure (see pictures below)
When i tried to publish that it failed and i got the error.
So instead i tried looping trough the first list and then again trough the second list and then appending it all and this fixed the issue for me. i now no longer have the Issue.
When having this Issue just disable different elements in your logic untill you can publish again and work back from there.
So when you need to go trough a list within a list in a structure this error is bound to happen.
Hello everyone,I encountered this error when trying to publish one of my applications. In the client action, I had disabled a block of commands to review them if necessary.I ended up deleting those commands, as shown in the figure I'm attaching below. After that, the publishing worked fine. That's crazy, isn't it?
Have a great day, everyone!
Today I got the same error. This happened when I changed a Server Action to a Client Action. So for now I'll keep them as Server Action.
I got the same error. In my case it was caused by a var of type Object Record List. An Object List works fine though. I'll report this bug to OS.
I ran into this error when I replaced a wrapper CRUD server action with the entity action (in a migration from an O11 _CS module to an ODC application). It gave me no warnings, but the mapping was completely fubar anyway.
I had to remove and re-add the entity action and map again. This solved my problem