Tip: How to avoid the compilation error "No data type with ..." after a Merge

Tip: How to avoid the compilation error "No data type with ..." after a Merge



After doing a merge or add reference operation in Service Studio, the compilation phase of the eSpace may stop with an internal error, issuing the a error message simliar to:

"Internal Error: No data type with for 'btEntityXXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX' and recordType '' could be found."

This will prevent compilation and thus, publication of the eSpace on the Hub Server


The workaround is to execute a forced refresh of the reference in question (if known) or of all references, to guarantee the consistency of the reference identifiers. Some rare cases may require to remove the reference and then add it again.

Nevertheless, always report to OutSystems Technical Support the occorrence of this error, by submitting the issue or sending us an email with the version of Service Studio used, the error message and the OML in question.

Thank you!

Best Regards

Miguel Simões João


This problem can also occur after a merge operation when some actions use parameters of Entity Identifier type. The error message that is generated during compilation is similar to

"Internal Error: Internal trace failure: No variable with id outXXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX."

The workaround is the same as mencioned in the previous post: forced refresh references.
Best Regards

Carlos Cabral