I have a Providence 2.09 installation that seems to be working apart from one thing. I have separate Excel mapping and data spreadsheets for the objects to be imported. The object mapping spreadsheet uses the entityJoiner refinery to import and map the entity information including attributes (idno, access, status, address [address1, address2, postalcode, etc.]), i.e.
entityJoiner mapping
{
"relationshipType": "^23",
"entityType": "^24",
"prefix": "^25",
"forename": "^26",
"other_forenames": "^27",
"middlename": "^28",
"surname": "^29",
"suffix": "^30",
"displayname": "^31",
"attributes": {
"idno": "^32",
"access": "^33",
"status": "^34",
"telephone": "^35",
"email": "^36",
"addressType": "^37",
"orgMDAcode": "^38",
"address": {
"address1": "^39",
"address2": "^40",
"city": "^41",
"county": "^42",
"postalcode": "^43",
"country": "^44"
}
},
"matchOn": ["idno"]
}
The object mapping spreadsheet also uses the storageLocationSplitter refinery to create and map the relationship to the Storage Location for each object, i.e.
storageLocationSplitter mapping
{
"relationshipType": "related",
"storageLocationType": "^45",
"attributes": {
"idno": "^46"
},
"ignoreParent": "1",
"matchOn": ["idno"]
}
Everything seems to work OK - the objects get imported and the relationships to entities and storage locations are built, except that if the address postalcode value is missing from the data spreadsheet then the object relationship to the storage location is not created. I've tried experimenting with leaving out different values and combinations of the entity address attributes but it's just the missing postalcode that causes the problem. All other objects are imported with the desired relationship to their storage location.
I could get around it by setting the postalcode value to dummy information, but I'd rather be able to leave it blank if the information is not known.
I'm attaching the full object mapping spreadsheet in case it's useful.
Many thanks for any help.
Berney
hc-mapping-object-v131.xlsx
