- Help Center
- API
- API Docs
-
Getting started
-
Integrations
-
PGA x Accelerate
-
API
-
Assortments & Catalogs
- Creating Order From Favorites- Using the Multi Delivery Board
- Digital Catalog Editor-Creating Your Digital Catalog
- How to Create an Assortment
- Adding a Canvas Page
- Linking a Showroom or Technical Video to a Feature Page
- Creating an Assortment with Embroidery
- Video Demo of Virtual Showroom
- Favorites List Workflow
- Multidate Orders using the Digital Catalog Enhancement
- Ordering From the Digital Catalog
- New Wish List Features
- Setting Permissions
- Browsing and Marking Up the Digital Catalog- Creating and Shopping a Favorites List
- Creating a Line Sheet
- Wish List Tutorial
- Wish List Cover Images
- New Assortments Tab
- FAQ's
- Catalog- Single Page Mode for Smaller Form Factors
-
Wholesale Order Entry
-
Accelerate
- RepSpark Go App
- Exporting My Orders
- Admin Dashboard
- Setting Up and Managing My Users
- Filling In and Uploading the Excel Sheets
- Filters and Sorting Products
- Getting Started
- Creating My Digital Catalog
- Adding My Images
- Reporting
- Exporting ATS to Excel
- Branding My Site
- Insignia Lite in Accelerate
- FAQ's- Really, FAQ's
-
Microsites
-
Admin
-
Data Management
-
B2B Users
-
Marketing
-
Reporting & Analytics
-
Software Updates
-
Internal
-
Community
-
RepSpark Pay
Sales person hierarchy for My Orders and Reports
My Orders and Reports allow multiple sales people, managers, and admins to view RepSpark orders in My Orders as well as ERP orders in Reports and Invoices.
For My Orders, the information needed to support this hierarchy comes from the ParentCode field in the Options API call. The top of the hierarchy has ParentCode set to NULL as they do not have anyone above them.
Here's a simple example.
- A (highest level)
- B (no children, one level deep)
- C (one child, one level deep)
- D (no children, two levels deep)
KeyCode ParentCode
A NULL
B A
C A
D C
For reports and invoices, the information needed is not represented as a recursive tree hierarchy in data. Instead, each individual report and invoice has a list of users allowed to see that report.
[{
"OrderNumber": "12345",
"Users": [{
"UserCode": "A",
"UserDescription": "A"
},
{
"UserCode": "B",
"UserDescription": "B"
},
{ "UserCode": "C", "UserDescription": "C" }, { "UserCode": "D", "UserDescription": "D" }]
}]
Again, the data for reports and invoices does not capture the exact hierarchy in the same parent/child relationship as Options. Each report and invoice needs to explicitly list the users that are allowed to view the report or invoice.