Getting Widget Conversion Errors While Publishing New App Version

Ask the Community
,
1

image
image468×646 38.7 KB

I’m getting these errors while publishing a new version of my app. There are errors for widgets that I am unable to find after too many tries. Can you please help me find out these errors or suggest any simpler method to find these errors or widgets?

Error Details

I’m encountering two widgetTemplateConversionError errors with ontologyNoLinkType:

Error 1:

{
“type”: “widgetTemplateConversionError”,
“widgetTemplateConversionError”: {
“widgetsOrigin”: [
“456285f3-8142-4007-8f50-84974b3a841b”
],
“error”: {
“type”: “ontologyNoLinkType”,
“ontologyNoLinkType”: {
“linkTypeId”: “ytijco2s.company-tasks”
}}}}

Error 2:

{
“type”: “widgetTemplateConversionError”,
“widgetTemplateConversionError”: {
“widgetsOrigin”: [
“2375b84e-369d-4553-8fd3-45b04a685fc4”
],
“error”: {
“type”: “ontologyNoLinkType”,
“ontologyNoLinkType”: {
“linkTypeId”: “ytijco2s.company-events”
}}}}

What I’ve Tried

I’ve tried locating these widgets multiple times but haven’t been able to find them in my application.

Questions

  1. How can I locate these specific widgets using their IDs (456285f3-8142-4007-8f50-84974b3a841b and 2375b84e-369d-4553-8fd3-45b04a685fc4)?

  2. What does ontologyNoLinkType mean? Are the link types ytijco2s.company-tasks and ytijco2s.company-events missing or incorrectly configured?

  3. Is there a simpler method to debug these types of errors in Workshop applications?

Any help would be greatly appreciated!

Thanks in advance

2

It might be possible that the link types are configured on a branch and are not available to be used in the main ontology until it is merged. Can you please check this?

1 Like
3

Thanks Sanjeeth,

The issue turned out to be different from what we initially thought, and it is now resolved.

The problem was within the workshop section itself. After trying several approaches, I started removing items one by one and testing each time. Eventually, I removed everything, and the error still appeared. I then deleted the entire section, recreated it from scratch, copied the required items back, and removed the old ones. After that, the error disappeared.

This workaround solved the issue, although the exact root cause is still unknown.