Thanks for the log.
This message tells that they didn’t observe the convention when defining custom parking position designators. As per documentation, you’d need a parking number besides the custom name of the parking location. They just provided the name alone. SODE will moan about this and will use the basic AFCAD/ADE data instead and ignores any custom namings. So it will continue to work for sure.
I have once inspected one of their files and found out that they still provide a file even if they don’t want to place jetways. So that SODE file is just a “placeholder” with empty jetway slots. They do that to have AES jetways displayed if the user chooses so during install.
You’d need to select the “SODE jetways” option in their installer so that the “populated” SODE file gets installed.
Cheers,
Jeffrey