We've ended up in a scenario where we have a DataType which depends on one of the built in Umbraco types, however the Guid Id that we have in our system does not match that in the uSync export XML files. As a result, trying to do an import fails with warnings. We're not sure how we ended up in this state?
It seems the Guid Ids for the built in types are static - so they should be consistent across different developers (we've confirmed this on another developer machine that our Ids are consistent).
Should we not use any of the built in data types when configuring our system?
Chad
05/23/2024, 12:49 AM
Got it - we had a merge resolution via git which malformed some of the xml files, so things didnt end up importing correctly.
Chad
05/23/2024, 12:49 AM
Wonder if there is a form of "strict mode" to catch this stuff earlier
k
Kevin Jump
05/23/2024, 6:09 AM
👍 - for info the guids shouldn't matter for uSync - if it can't find it by guid it will look for datatypes by alias, then fix the guid on the target system to match wehat is in the files.
we certainly use to have some checks for merge conflicts, the uSync health checks might still pick that up.