Hi Eric,
we are getting this message when we try to publish from the Object Designer:
“No. is not a valid anchor on page”
Unfortunately it does not mention which page this is related to.
I checked all fields we created and changed all anchors where we used “No.” before.
Even on older fields we created months ago where this was not an issue until now.
But the error still appears. I am running out of ideas, can you help us?
This is the full error message:
Fehlermeldung:
No. is not a valid anchor on page
Interne Sitzungs-ID:
55a7b1c9-4fa8-4119-98c7-18369ff04eba
Application Insights-Sitzungs-ID:
4af5e229-e2be-43d5-9df3-0e71c4e112d9
Client-Aktivitäts-ID:
9b9cfb3e-6792-4794-b94c-cfcf06698e4a
Zeitstempel bei Fehler:
2024-10-10T08:07:22.5248692Z
Benutzertelemetrie-ID:
1472876a-55ca-4f0e-a40b-b425c47ece25
Al-Aufrufliste:
“Build Extension Hgd”(CodeUnit 70310250).VerifyThanAnchorExist line 16 – Simple Object Designer by Hougaard
“Build Extension Hgd”(CodeUnit 70310250).ExportPageExtensions line 91 – Simple Object Designer by Hougaard
“Build Extension Hgd”(CodeUnit 70310250).CreateExtensionEx line 244 – Simple Object Designer by Hougaard
“Object Designer Menu Hgd”(Page 70310263).”ExportExtension – OnAction”(Trigger) line 8 – Simple Object Designer by Hougaard
Please use the “Export App” function from the setup page and send me the json file, then I’ll take a look at it.
This is an error from one of your Features. Try going through your features and click the “Verify Feature” function.
Sorry, actually could also be because you have specified an invalid anchor when placing a field.
Try the following:
1. Go to the SOD Setup page and use “refresh symbols”, answer Yes to clear the cache.
2. Go through all field placements, and make sure that the anchor specified exists in the lookup.
/Erik
I tried this as you described and additionally reselected every anchor from the lookup to make sure there is no invalid anchor.
None of the fields had “No.” as an anchor. But still the error message persists.
The Designer doesn’t even allow me to download the sourcecode from the setup page, the same error appears if I try to do that.
Is there anything else that I might be missing?
My fallback solution would be to initialise a new app in a sandbox and rebuild the app, but we would really prefer to avoid that, since that would mean migrating field data and changing reports that use SOD-APIs. And of course it would take some time.
Hi Eric, I tried this, but sadly it didn’t change or prevent the error message.
There were no changes to our features before I tried to publish. The changes we wanted to publish were related to custom fields on existing tables.