<maximo-datasource depends-on="woDetailResource" id="emxWoHazards" relationship="wohazard" selection-mode="none" notify-when-parent-loads="true" object-name="wohazard">
<attribute name="wohazardid" unique-id="true"/>
When viewing the app in the web, this causes a separate API request to be made to retrieve the data. In Mobile we combine these dependent data sources into a single request to ensure they all complete or fail together. As for the invalid XML, that's really hard to tell without seeing it. Our validation checks more than just that it's valid XML syntax in the traditional sense (such as closing tags). We're checking that the XML is actually valid for our framework such as elements are only nested in controls they're allowed to be nested inside. Utilizing Application Designer terminology, you can't utilize a textbox for a table column, you have to use the tablecol control. Make sure you're using the right version of the docker image for your version of Maximo Mobile. That will vary based on even the IFIX of Maximo Mobile installed. IE if you install Maximo Mobile 8.6.0 IFIX 01 you need to be on 8.6.3 of the docker container. You should get a warning if there's a mismatch on the graphite version between the container and your environment on newer versions of the configuration utility and since you have the properties editor you're at least on the 8.6.0 version of the configuration utility.