[SOLVED] uSync - v8 - Not adding a property to a d...
# help-with-umbracon
Nik
10/12/2023, 8:54 AMI've got a site that has uSync installed, however when I run an import it is not adding a property to a document type.
The property can be seen in the Schema file for the document type, it shows as missing in the report, but after the import (which completes successfully) the property is still missing. Does anyone have any ideas what could cause this?
I'm currently doing a fresh deployment of the site to see if that resolves the issue.
k
Kevin Jump
10/12/2023, 9:01 AMMissing package?
n
Nik
10/12/2023, 9:01 AMNope, it's core data type it's using
m
Mike Chambers
10/12/2023, 9:02 AMnot a legacy core data type perhaps?
n
Nik
10/12/2023, 9:02 AMNah, it's MNTP
m
Mike Chambers
10/12/2023, 9:02 AMdoes it have a start node set that doesn't exist?
n
Nik
10/12/2023, 9:03 AMThis one is configured to allow for any page in the site to be picked, no limitations on numbers/types/start nodes
Nik
10/12/2023, 9:03 AMThe same data type is used on mupltiple pages already, just this one doesn't want to add unfortunately
k
Kevin Jump
10/12/2023, 9:03 AMI would check the data type exists on the site as you would expect (eg right name etc)
Kevin Jump
10/12/2023, 9:04 AMDoes it exist on a component that the doc type might use (in a different tab or group?)
n
Nik
10/12/2023, 9:11 AMI'm going hunting 🙂 It looks like the defintion file is missing from the repo, but historically people were using usync complete to push settings (I don't because it's resulted in the repo becoming out of sync with what's actually there) - so although the data type is in use in places, the usync definition file isn't getting deployed!
Nik
10/12/2023, 9:12 AMThank you both for pointing in the right direction 🙂 I'll confirm if it all starts working once the file is present
Nik
10/12/2023, 9:43 AMSo it looks like it was related to the missing file and something odd going on with what should have been the data type being used. All sorted now 🙂 Thanks everyone