TODO
UPDATE FOR PIMICS 13.0 - CUSTOMIZATION COMPATIBILITY:
Database Schema Changes: Document the following table/field changes that may affect custom extensions:
- Publication Document tables: New feature and keyword fields added
- Cross-Reference tables: New fields for type code, description, and translations
- Category History tables: New archive tables for Item Groups, Product Groups, Chapters, Catalog Groups
- Pipeline tables: Completely new tables for workflows, processes, stages, actions
- Entity tables with pipeline status: Items, publications, etc. now have pipeline tracking fields
Event Changes: Document events that may have new parameters or behavior changes:
- Publication versioning events (create/restore/delete)
- Document handling events
- Cross-reference management events
- Custom field/table events in publications
Extension Points:
- Bulk edit extensibility for new entity types (Item Groups, Product Groups, Chapters, etc.)
- Mass edit card extensions for publication lines
- Pipeline action framework for custom actions
- Export mapping source type validation extensions
Upgrade Considerations:
- Provide specific table names and field names that changed
- List all new enums and their values
- Document any deprecated fields or objects (even if none in 13.0)
- Create testing checklist for common customization scenarios
- Provide rollback guidance and compatibility testing procedures
Code Samples:
- How to subscribe to new publication events
- How to extend bulk edit for custom entity types
- How to create custom pipeline actions
- How to handle new API fields in integrations
Action required:
- Create "Upgrading to 13.0" guide with technical details
- Document all table/field schema changes
- List breaking vs. non-breaking changes
- Provide migration scripts if needed
- Add compatibility testing guide
Download
You can download pimics from https://alliumsro.sharepoint.com/sites/PimicsDev/Public. If you don't have an access please contact your us on info@pimics.com or your contact person in Allium.
Extensions
Important
In version 12.1 we will use depandency on a new extension calls Pimics Base.
| Name | Id | Object range |
|---|---|---|
| Allium Core | ||
| Pimics PIM | ||
| Pimics - Vendor Catalog | ||
| BMECat for Pimics | ||
| DataNorm for Pimics | ||
| Pimics AI | ||
| Pimics on-prem | ||
| Pimics Base | 5912d464-24c8-4816-b552-3c97e3144eee |
Diagram
graph TD
PIM[Pimics PIM] --> AC[Allium Core]
OP[Pimics on-premise] --> PIM
AI[Pimics AI] --> PIM
VC[Pimics - Vendor Catalog] --> PIM
VC --> AC
BME[BMEcat for Pimics] --> VC
BME --> PIM
DN[Datanorm for Pimics] --> VC
DN --> PIM
Pimics Base
Will contain tables and interfaces that needs to be shared across different extensions.
Diagram after Pimics Base
graph TD
PIM[Pimics PIM] --> AC[Allium Core]
OP[Pimics on-premise] --> PIM
AI[Pimics AI] --> PIM
VC[Pimics - Vendor Catalog] --> PIM
VC --> AC
BME[BMEcat for Pimics] --> VC
BME --> PIM
DN[Datanorm for Pimics] --> VC
DN --> PIM
PIM --> B[Pimics Base]
VC --> B
DN --> B
AI --> B
BME --> B
OP --> B
Pimics on-premise
Before you can install Pimics on-premise extension you need to upload add-ins.
- Open folder Releases is folder Add-ins (see downloads)
- Copy the content of this folder into Add-ins folder in service. Typically it is C:\Program Files\Microsoft Dynamics NAV\180\Service\Add-Ins\ (replace version 180 with your current version)
- Or you can use our script CopyToAddInFolder.ps1 and specify the parameter -version.
- Restart the service
- Install extension