Source file: JSON formatted

UnitySync continues to add to our supported directory types, including ldap, o365, odbc, ldif and csv.

As of v4.7.18 we’ve added support for source directory type of Json.

The JSON source:

JSON is supported via a Json formatted source file. This may be used as the source to sync into all supported directory types.

Below is a sample import.txt file containing two records. The attribute names would be replaced by appropriate attribute names from your own source data file. Unitysync custom mapping can be used to map any attribute name in your import.txt file. (Ideally a unique and unchanging attribute value will be used as index. If an ID is not available for use as an index, the email address may work). We recommend you start with a small JSON file to test your intial syncs.

[  
  {  
    "AnIndexAttribute": "1001",  
    "Displayname": "Joe Smith",  
     "LastName": "Smith",  
     "FirstName": "Joe",  
     "email": "Joe.Smith@domain.com",  
     "mobilephone": "555-555-1234",  
     "ProxyAd": ["SMTP:Joe.Smith@domain.com", "smtp:JSmith@domain.com"], 
     "Department": "Sales"  
  },  

  {
     "AnIndexAttribute": "1002",
     "Displayname": "Sally Jones",
     "LastName": "Jones",
     "FirstName": "Sally",
     "email": "Sally.Jones@domain.com",
    "ProxyAd": ["SMTP:Sally.Jones@domain.com", "smtp:SJones@domain.com"],
     "mobilephone": "555-555-1234",
     "City": "LA",
     "State": "California"
  }
]

Creating and configuring a connection with a JSON source.

1. Generate import.txt with the records you’d like to sync.

2. In the UI, click NEW to create a new connection. Select the Source Template JSON and Source Engine JSON. Select the desired Destination Template and Engine. Enter a connection name and click Save.

3. The source JSON formatted file must be named import.txt and located in the Connection directory i.e. \Connections\Json-to-AD\import.txt

4. On the source tab, fill Field Definitions based on your source data.

5. On the Destination tab, fill in your destination directory information.

6. Click Save.

7. Above are the minimum setings to test your connection. Now, On the General tab, click Discovery, you should see the correct number of records discovered. Next click Simulation. You should see the appropriate number of ADDS specified. Click Sync, confirm the Adds were successful and also view the destination contacts directly to confirm.

8. This step explains how to configure a Custom Object Map file to any/all import.txt data to sync to your destination directory attributes. On the Custom tab, click Object Map. Fill in a name for the map file and click OK. In this file, edit/add mappings to suit your destination directory attributes and source JSON file attributes. Click Save. Click Save again.

9. Finally, run your Discovery and Sync again. You should see objects Modified to contain the new data as mapped. If necessary, edit the custom map futher.