Migration NJSON File Find & Replace (Alpha)

Updated January 16, 2023 20:39

Note: This product is in Alpha, which means it may change frequently and it is possible that your unique file will cause errors. Be aware and check the files it produces and reach out to Ordergroove Support if there are any issues.

Data File: Any valid Ordergroove migration NDJSON file.
Actions File: Action and condition JSON file (structure detailed below). You can have unlimited actions and unlimited conditions per action.

[
    {
        "type" : "replace",
        "object" : "payments",
        "origin" : false,
        "key" : "token",
        "value" : "new_payment_token_123",
        "conditions" : [
            {
                "object"  : "customer",
                "key" : "email",
                "operator" : "eq",
                "value" : "match_on_email@email.com"
            },{
                "object" : "this",
                "key" : "id",
                "origin" : true
                "operator" : "eq",
                "value" : "old_payment_token"
            }
        ]
    },{
        "type" : "replace",
        "object" : "customer",
        "origin" : false,
        "key" : "email",
        "value" : "take_acton_on_email@this.com",
        "conditions" : [
            {
                "object" : "this",
                "key" : "merchant_user_id",
                "operator" : "eq",
                "value" : "user_to_match"
            }
        ]
    } 
]

For Every Action

Field	Description	Type
type	What type of action to take. Currently, there is only one option —replace: replace the current value with the indicated value	string
object	Which object in the customer's migration data to execute the action on. Options: customer payments addresses subscriptions	string
origin	Indicates whether the key points to a value in the origin object	boolean
key	The key of the value to take the action on	string
value	The value to use with the action 'eg replace existing value of key with this value'	string
conditions	Conditions under which the action will be taken on an object. If action should be taken on every object - leave conditions as null.	list of objects or null

For Every Condition

Field	Description	Type
object	Which object in the customer's migration data to evaluate the condition on. Options: customer payments addresses subscriptions	string
origin	Indicates whether the key points to a value in the origin object	boolean
key	The key of the value to take the action on	string
value	The value to use with the action 'eg replace existing value of key with this value'	string
operator	The type of evaluation to be made. Options: eq: is the value indicated by the action equal to the value indicated by the condition len-less: does value indicated by the action have fewer characters than the condition value (value should be number sent as string eg- "10") len-more: does value indicated by the action have more characters than the condition value (value should be number sent as string eg - "5")	string

bool

Select an action and data file and click the Process File button. You will be prompted to download two files:

updated_data.json: A new version of the data file you selected
update_log: A log explaining what was checked on each customer, the result of the conditions, and what action was taken if any.

Select Actions File Select Data File

Process File