Jasper PIM: General Do's & Don'ts

DOs

  1. DO Check the Jobs Table Before Running Batch Actions or Mass Syncs: 

  • Always verify the jobs table to ensure no conflicting processes are running. This helps prevent unnecessary double uploads and overwriting issues. 

 

  1. DO Consider the Capacity of Your Environment: 

  • If you have a dedicated environment - remember that while it can handle significant stress, there are limits. Plan your mass syncs, imports, and bulk updates accordingly to avoid overloading the system. 

  

  1. DO Utilize the Communication Logs for Troubleshooting: 

  • When synchronizing information, always check the Communication Logs table. Viewing details under the Debug column can help you troubleshoot issues, often related to the platform you’re syncing with. 

  

  1. DO Validate CSV Files Before Uploading: 

  • Always validate your CSV files before running large imports. A test upload of a single product is recommended to ensure everything is correct before committing to bulk actions. 

  

  1. DO Verify Asset Links Are Public Before Uploading: 

  • Whether uploading assets via CSV, UI, or API, ensure that the asset links are public. Non-public links will result in failed uploads. 

  

  1. DO Assign Slugs to Attribute Fields in CSV Profiles: 

  • Ensure that any attribute fields you want to update have a slug assigned. Missing slugs will cause the importer to fail and prevent you from saving the profile. 

  

  1. DO Save Your API Keys Immediately: 

  • Remember to save your API keys as soon as you create them, as they are only visible once. 

  

  1. DO Refer to the Knowledge Base or Seek Training for Unfamiliar Tasks: 

  • If you are unsure about any operation within Jasper PIM, always refer to the knowledge base or contact Jasper support for training before proceeding. 

Knowledge Base 

  

  1. DO Ensure Correct Scopes When Creating API Keys for Channels: 

  • When generating API keys for channels, double-check that the correct scopes are assigned. Incorrect scopes will result in denied requests for updating product information. 

  

10. DO Enable 'Auto Categories' for Auto Categorization: 

  • When using the auto categorization feature, ensure 'Auto Categories' is turned on in the category’s details tab before saving. 

  

11. DO Allow Time for Auto Categories to Update: 

  • After enabling auto categorization, wait 1-2 minutes before checking to ensure the changes have been applied, as this process runs on a CRON job. 

  

12. DO Check the Scheduled Content Tab Before Making Changes: 

  • Always review the scheduled content tab to verify that upcoming changes haven’t already been applied. This avoids redundant updates. 

  

13. DO Save Frequent Search Filters as Projects: 

  • If you often use the same query filter in product search, save it as a project for quick access. Projects can be independent of workflows and serve as a handy tool for efficiency. 

  

14. DO Verify Product Publication Status Before Syncing: 

  • Always confirm that a product is set to "Published" on the product screen before syncing it to a channel. This is your final safeguard to ensure the product is properly synced. 

DON’TS

  1. DON'T Run Multiple Intensive Processes Simultaneously: 

  • Avoid running multiple mass syncs, price imports, bulk updates, and other intensive processes at the same time. Overloading the system can lead to performance issues and delays. 

  

  1. DON'T Overlook the Communication Logs for Sync Issues: 

  • Ignoring the Communication Logs can lead to missed troubleshooting opportunities, especially when syncing data with external platforms. 

  

  1. DON'T Skip CSV Validation Steps: 

  • Skipping validation and test uploads before bulk importing can result in widespread errors that are difficult to correct. 

  

  1. DON'T Upload Non-Public Asset Links: 

  • Attempting to upload assets with non-public links will fail, wasting time and resources. Always check link visibility first. 

  

  1. DON'T Forget to Assign Slugs in CSV Profiles: 

  • Neglecting to assign slugs to attribute fields in your CSV profiles will prevent the import from proceeding, causing unnecessary delays. 

  

  1. DON'T Misplace Your API Keys: 

  • Failing to save your API keys immediately after creation means you won’t be able to retrieve them later, potentially disrupting integration work. 

  

  1. DON'T Proceed Without Checking the Knowledge Base: 

  • Attempting tasks you’re unsure of without consulting the knowledge base or Jasper support can lead to errors and complications. 

  

  1. DON'T Assign Incorrect Scopes to API Keys: 

  • Incorrectly scoped API keys will result in failed updates and wasted effort. Double-check scope settings when creating keys. 

  

  1. DON'T Forget to Turn On 'Auto Categories': 

  • If 'Auto Categories' isn’t enabled in the details tab, your auto categorization efforts will not be applied, leading to confusion and inefficiency. 

  

10. DON'T Check Auto Categories Too Soon: 

  • Checking for auto categorization updates immediately after saving might show incomplete results. Always allow 1-2 minutes for the CRON job to run. 

  

11. DON'T Duplicate Scheduled Content Updates: 

  • Failing to check the scheduled content tab before making changes can lead to redundant updates, which are inefficient. 

  

12. DON'T Run Bulk Actions Without Verifying Search Filters: 

  • Always verify that your search filter is accurate before running bulk actions. Incorrect filters can lead to unintended changes across products. 

  

13. DON'T Attempt to Sync Unpublished Products: 

  • Syncing products that aren’t marked as "Published" will fail, even if they’re enabled on channels. Always verify publication status first.Â