Hi,
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?