Good afternoon,
I am getting these errors when I attempt to publish the Directory application of the O11 to ODC course for the first time:
The first time, I installed the application without any issues. Until I came across the error from this post: https://www.outsystems.com/forums/discussion/104504/from-o11-to-odc-course-invalid-credentials-trying-to-login-to-directory-app/
After I attempted to solve this error manually, I still had some issues, so I decided to fully delete the application from the portal and reinstall it. After I deleted the Directory application, I closed everything (and once even restarted my laptop for what it's worth) and reopened the Directory file directly from the course (also after downloading it, unzipping it, and removing all potential blockages). After this, I got the errors mentioned at the start of this message.
I've attempted this multiple times and got the same error over and over.Some other things that caught my attention:
Does anyone know how to solve these errors? Thanks a lot in advance!Cheers,Fabian
Hi Fabian,
You’re getting the “Open in Browser” error because, even though the app exists in your environment, it hasn’t been successfully published. Since the deployment failed, the application isn’t actually available yet, so it can’t be accessed in the browser.
Regarding the deployment errors:
These are mentioned in the ODC release notes: ( success.outsystems.com/support/release_notes/outsystems_developer_cloud_releases/outsystems_developer_cloud/ )
___
After checking the OML, it looks like the issue is caused by the Joins between Employee and EmployeePicture. I’m not entirely sure why this triggers the error, but removing those Joins allowed the application to publish successfully.
I’ve attached an updated OML that fixes the deployment errors and also includes the built-in community login.
Hi Mihai,
Thanks a lot for your time and the extensive reply. The "Open in Browser" error makes a lot of sense to me now. The release notes however state which cases for these errors were fixed. I couldn't really get much use out of it myself. I couldn't open your updated OML, because it was created in Service Studio according to the error message.
I was about to have a look at the joins, but wanted to try my luck at publishing just before that and managed to do so successfully without any issues. Does a laptop restart have any influence on the publish button? I haven't made any changes at all since I posted this last Friday.
Cheers,
Fabian
Hi,
No, a laptop restart itself doesn’t fix publish errors. I just tested again with the joins included, and the issue seems to have disappeared. Since I also reported it on Friday, it’s possible that OutSystems introduced a fix in the meantime.