Recommend Configuration for Pimics in Business Central
Retention Policy
Pimics collect certain data that should be periodically clean up. The below is a table with suggested configuration. To define it please follow steps: Set up a retention policy.
| Table | Table No. | Suggested Retention Period | Description | Suggested Parameters |
|---|---|---|---|---|
| Master Data Change Log | 70113732 | Weekly | Master Data Change Log contains all the information about data changes in Pimics. It is used for background processes. it is not necessary to keep it for long periods. | - |
| Activity Log | 70113724 | Monthly | Potential issues and errors are saved to this log | - |
| Publication Queue | 70113734 | Weekly | For integration to Shopify or when Pimics send request to API. Pimics sends requests through this table. When there is no error, it doesn't make sense to keep it. | Only when State is Done |
| Publication Line Change Log | 70114174 | Weekly | Information for 3rd party integrations about the changes in Publications. Usually, they read this info at least hourly | - |
History | There is locked predefined filters Publication Line Archive | No possibility to keep latest Publication Price Archive | No possibility to keep latest
Job Queues
Pimics contains lots of codeunit and reports to run certain actions on a backgound as a Job Queue.
| Object | Description | Parameter String | Additional Links |
|---|---|---|---|
| codeunit 70113790 "PIMX Job Full Upd Publication" | On select publications (parameter -CODEFILTER) run selected actions. We recommend to use at least -REORGANIZE or -UPDATE. | -CODEFILTER publicationcode -LOCK -RELEASE -REORGANIZE -UPDATE -PUBLISH | Refreshing the publication data |
| codeunit 70113798 "PIMX Job Send Publ. Queue" | It takes records in Publication Queue and send them to APIs | nothing | - |
| codeunit 70113818 "PIMX License Job" OBSOLETE | It periodacaly call our license service to get the newest pimics license | nothing | - |
| codeunit 70113878 "PIMX Rule Job" | Process Rules on Features that have been changes since the previous success run. This codeunit should be defined only once. | nothing | Rules |
| codeunit 70113888 "PIMX Job Upd. Publ.By Log v10" | It goes through Master Data Change Log and reorganize selected publications (parameter -CODEFILTER). It updates only lines that has been modfied in master data (see fields Publication State and Publications in the log). Parameter -FIRSTRUN will not reorganize any lines, but sets internal states that all changes have been processed. This codeunit should be defined only once. | -CODEFILTER publicationcode -DEBUG -BATCHSIZE -FIRSTRUN | Refreshing the publication data |
| codeunit 70113898 "PIMX Job Publ. Lines Cleanup" OBSOLETE | |||
| report 70113723 "PIMX File Sync SharePoint" | Synchronize 1 SharePoint library with Pimics. It reads the whole library to create or update documents. | Use Reqest Page | SharePoint configuration |
| report 70113736 "PIMX Refresh DA Metadata" | On existing files it calls the repository and update the metadata of the file. The same action as on pages Refresh Metadata | Use Reqest Page | - |
| report 70113740 "PIMX SharePoint Delta Sync" | Retrieves changes from a SharePoint library by using the timestamp of the last successful synchronization | Use Reqest Page | - |
Change Log
Configuration Templates