A rule in the model references a field with an absolute path
However, this leads to problems in the generated relationship model,
because the include makes the root group “target”
This cannot be resolved with a relative path, as seen in an error condition
This can however be resolved in two ways:
-
Make sure, that your field names are unique, so that using a field name will not be ambiguous and so a path-indicator is not necessary
-
In the generated relationship model, mark the include to not contain any validation rules
The preferred solution would be option 1, because same name fields could potentially cause problems elsewehere.





