I got the new dataset with the renamed tables for the REST endpoints from deployment and I used it to export the REST endpoints and data definitions to our acceptance environment. But I noticed that it skipped a few data definitions.
Upon further inspection I found out that it only got the data definitions which belong to a REST endpoint. I also have nested data definitions which don’t belong to a REST endpoint but do belong to a data definition as a field.
For instance I have a relations REST endpoint with a relations data definition, in the relations data definition I have a field accessibleRelations which is a nested data definition. On the acceptance environment it didn’t import the accessibleRelations field under the relations data definition.
I got it working with a work around by explicitly creating a REST endpoint for the accessibleRelations data definition and then deleting this REST endpoint again in our acceptance environment after I checked that the field was now correctly imported under the relations data definition.
Is this expected behaviour or should it import nested data definitions as fields regardless of the fact that there is no REST data endpoint for it?
If data definitions can be nested, I think the expected result is to have the nested data definitions to be in the export as well. This might be a bug, please create an SR for it so we can have better look.
Could you please check if the sub data definitions are linked at the top level of the Endpoint?
If you navigate to the REST Endpoint and click on “Data Definition”, you’ll find a grid that shows whether all nested data definitions are correctly linked. Please note that this grid might be hidden in the menu on that page, so make sure to expand or check the available menu options.
The Dataset relies on this table. If the grid is empty or incomplete, please click on “Determine” to populate it.
That did the trick for one of the two nested fields. Namely the Address nested dataset. But I also have an AccessibleRelations nested dataset inside my Relations dataset which doesn’t show up when I press the “Determine” button.
The only difference between the two is that Addresses is a single object and AccessibleRelations can be multiple objects.
To figure out what’s the issue we would need to trace this. I suggest we take this up in the created SR. After the problem is found we will update this post with the information.