Supported Prefixes of Metadata Saved Searches IDs in NSPB Sync
Make sure the IDs of the cloned saved searches start with the following prefixes. The cloned saved searches shouldn't use any of these prefixes as their IDs.
|
Saved Search Type |
Supported Prefixes |
|---|---|
|
Item |
customsearch_nspbcs_sync_item |
|
Vendor |
customsearch_nspbcs_sync_vend |
|
Subsidiary |
customsearch_nspbcs_sync_sub |
|
Location |
customsearch_nspbcs_sync_loc |
|
Income Statement Accounts |
customsearch_nspbcs_sync_acct_inc_stmt customsearch_nspbcs_sync_acis |
|
Balance Sheet Accounts |
customsearch_nspbcs_sync_acct_bs customsearch_nspbcs_sync_acbs |
|
Class |
customsearch_nspbcs_sync_class customsearch_nspbcs_sync_clss |
|
Customer |
customsearch_nspbcs_sync_cust |
|
Department |
customsearch_nspbcs_sync_dept |
|
Project |
customsearch_nspbcs_sync_prj |
|
Customer Project |
customsearch_nspbcs_sync_cprj |
|
Employee |
customsearch_nspbcs_sync_emp |
Related Topics
- Metadata Export from NSPB Sync to Planning and Budgeting
- Supported Metadata Saved Searches in NSPB Sync
- Item Metadata in NSPB Sync
- Vendor Metadata in NSPB Sync
- Location Metadata in NSPB Sync
- Accounts Metadata in NSPB Sync
- Class Metadata in NSPB Sync
- Customer Metadata in NSPB Sync
- Department Metadata in NSPB Sync
- Project Metadata in NSPB Sync
- Customer Project Metadata in NSPB Sync
- Employee Metadata in NSPB Sync
- Subsidiary Metadata in NSPB Sync
- Custom Segment Metadata in NSPB Sync
- Creating the Hierarchy of Metadata in NSPB Sync
- Optimal Number of Metadata Records to Import from NSPB Sync to Planning and Budgeting
- Returning Metadata Hierarchy Based Only on Cloned Saved Search in NSPB Sync
- Account Type Mapping in NSPB Sync
- Item Type Mapping in NSPB Sync