2022

Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

Pre-Requisites

Database should have three columns to store Parent Name (type: String), Child Name (type: String) and Hierarchy level (type: Integer)  

Integration

Database

QuickBooks

Parent Name

Customer

Child Name

Job

Hierarchy

Sub level

For Integration from Database into QuickBooks

  • If Quickbooks Customer has hierarchy structures enabled, then the following changes have to be implemented within your DBSync mappings to facilitate hierarchy mappings.
  • Let's say Avankia & DBSync are the Parent Name & Child Name in Database then Avankia & DBSync are Customer & Job in QuickBooks respectively.
  • Go to the location where pdl is present and open the workflow where Customer hierarchy mapping to be done
  • Based on hierarchy level the number of sequences has to be created with in the workflow.
    • Example: If hierarchy level is 2 then three sequences has to be created  with in the workflow
  • The first sequence validate row should contain a condition to check ParentRef field which contains Customer name so that the mapping for the sequence works
    • Example : IF(ISEMPTY(VALUE("ParentRef/ListID")),"true","false")
    • Map Name field of QuickBooks to Parent Name column in Database for the first sequence
    • Example : Parent Name - VALUE("Name")
    • Map Sublevel field of QuickBooks to Hierarchy column in Database. If Sublevel value is 0 then it refers to Parent Name
    • Example: Hierarchy - VALUE("Sublevel")
  • The Second sequence validate row should contain the condition to check for the hierarchy level 1
    • Example : IF(ISEMPTY(VALUE("ParentRef/ListID")),"false",IF(EQUALS(VALUE("Sublevel"),"1"), "true","false"))
    • Map Name field of QuickBooks to Child Name column in Database
    • Example: Child Name - VALUE("Name")
    • Map QuickBooks Customer Name with the Parent Name column in Database
    • Example : Parent Name - LSPLIT(VALUE("ParentRef/FullName"),":")
    • Map Sublevel field of QuickBooks to Hierarchy column in Database. If Sublevel value is 1 then it refers to first Child Name
    • Example: Hierarchy - VALUE("Sublevel")
  • Third and other sequence depends upon the number of Sublevel ie the hierarchy level of the Child Name
    • If the hierarchy level is 2 then configure the third sequence with the following trigger and so on
    • Example : IF(ISEMPTY(VALUE("ParentRef/ListID")),"false",IF(EQUALS(VALUE("Sublevel"),"2"), "true","false"))
    • Map Sublevel field of QuickBooks to Hierarchy column in Database. If Sublevel value is 2 then it refers to second Child Name
    • Example: Hierarchy - VALUE("Sublevel")
  • Once the above sequence are added, save and close the workflow


  • No labels