Release notes: Pimics 9
Content
On this page: (Top, Pimics PIM, Pimics Vendor Catalog, Pimics on-premise) Other versions: Pimics 8
Pimics PIM
(Top, Pimics PIM, Pimics Vendor Catalog, Pimics on-premise, BMECat for Pimics)
Pimics PIM 9.2.6
Bugfixes:
| Identification | Title | Notes |
|---|---|---|
| #25207 | Inherit Feature Values - not overtaking values | |
| #25284 | Repository type Link requires container setup |
Pimics PIM 9.2.5
Bugfixes:
| Identification | Title | Notes |
|---|---|---|
| #25300 | change to the extended text is not reflected in the publication | |
| #25141 | Set proper Data Caption Expression for Select User Filter/Filter by Classification | |
| #25139, INC-006994 | Localized version of TinyMCE for AlliumHTMLEditor Add-In | |
| #25229 | Fix Translation to DE | |
| #24450 | Feature - The length of the string is 22, but it must be less than or equal to 20 characters. Value: 'PEVNOST HORIZONT (A)' | |
| #25334 | Export Translation API - Features / Value |
Pimics PIM 9.2.4
Bugfixes:
| Identification | Title | Notes |
|---|---|---|
| #24566 | Auto. Tests: PIMX Test Publication: The Publication Line does not exist | Related issue #25072: Sister Line - Call ProductDataIsDone and ProductIsDone allowing to modify the record |
| #24991 | Rename Value ID - impact on PF.Value ID, Value Set line | |
| #25048 | PF: Item cannot be deleted when Inherited Product Feature exists | |
| #25054 | Get Deleted Lines doesnt work | |
| #25055 | Get Features produces error | |
| #25070 | Product Feature.Number validate - performance | |
| #25082 | Move Product Feature FactBox on Item List out of beta | |
| #25113 | Search and available pages | |
| #25127 | Assign To Category: modify triggers are invoked even if not needed | |
| #25136 | Product Feature Value Set - not being added any values | |
| #25149 | Export Mapping - API Translation - Description - Translations are exported wrong or not at all | |
| #25155 | Resolvertype is not set correctly after certification | |
| #25179 | Publicaiton Line Date Modified is set in different order then expected | |
| #25220 | Wrong URL when Refresh Metadata | |
| #25290 | Field Relevance and Element in the publication line |
Pimics PIM 9.2.3
Bugfixes:
| Identification | Title | Notes |
|---|---|---|
| #25017 | Update On c1 - impact on existing customers | |
| #24277 | Export Mapping - API Translation - Description |
Pimics PIM 9.2.2
Bugfixes:
| Identification | Title | Notes |
|---|---|---|
| #24440 | Publication Channel - Reorganize Sister - don't jump to reorganize main product | |
| #24664 | Product Feature - performance | |
| #24666 | Publication: PugGroup Reference - Index is out of bound - merge issue (?) | |
| #24698 | Product Feature: Open Value - wrong filter | |
| #24838 | Units: The source record has Translations disabled; line cannot be added |
Pimics PIM 9.2.1
Bugfixes:
| Identification | Title | Notes |
|---|---|---|
| #24489 | Translation Type is not being changed | |
| #24609 | Role Center: PIMX Item List caption | |
| #24634 | Refresh values on product features | |
| #24637 | Upd. Publ. API set as Access = Internal |
Vendor Catalog 9.1.1
Bugfixes:
| Identification | Title | Notes |
|---|---|---|
| #24010 | Modificaton of the Destination field in "PIMX Excel Mapping Line" (Excel mapping) | |
| #24128 | Item activation - EAN not included | |
| #24505 | Import via Import Mapping fails if Transf. Params are defined | |
| #24523 | German translation of progress label is missing placeholder for percentage | |
| #24755 | Length of Vendor Feature.Value < Product Feature.Value |
Pimics PIM 9.2
New Features
Excel export mapping created from template file
To make working with Excel exports easier, we give the users a new tool: creating the export mapping starting from an Excel template file. So now you can either create a mapping from scratch and work through it field by field, column by column, or directly specify a template Excel file, from which Pimics will create your export mapping. Increased productivity and ease of use.
Rules for features
Users are now able to process product features according to rules they define. The first option already available is Units Conversion. Other options for feature values processing will be added.
Optimizations to existing processes:
| Identification | Title | Notes |
|---|---|---|
| #22135 | Value Set on Feature/Product Feature | It ispossible to define different value sets for the same feature and use it in on Items and Categories |
| #21604 | New action on Item: Refresh Publications | |
| #20899 | Change the state (Certifed ⇒ Process) when item data changed | |
| #22688 | Map existing Documents on external IDs | |
| #21943 | Identify the lines with issues during upg. PF → CF | |
| #21794 | API Translation - Wert is not populated | |
| #20219 | Merge Values for product/catalog features and other links | |
| #11604 | Publication - Insert entity without children | |
| #17231 | Create Item Group from Items | |
| #20821 | BMECat import update | |
| #21052 | "Certify Vendor Item" report | |
| #21130 | Refinements in working with links | |
| #21234 | "Refresh Metadata" report | |
| #21237 | "Move Digital Assets to Default Repository" report | |
| #21242 | RefreshMetadata - Links |
Bugfixes:
| Identification | Title | Notes |
|---|---|---|
| #24207 | Publication Channel Card: Fix BMECat options visibility and captions | |
| #23993 | BMECat - UDX.EDXF.MIME_FILENAME extraction at file import |
Pimics PIM 9.1.9
Bugs
| Identification | Title | Notes |
|---|---|---|
| Upgrade 9.1.7 to 9.2.0 is not possible | UnprocessableEntity. Reason: Could not upgrade the extension 'Pimics PIM' by 'Allium' from version '9.1.8.0' to '9.2.0.0' due to the following error: 'An invalid argument was passed to a 'List' data type method.' |
Pimics PIM 9.1.8
Bugs
| Identification | Title | Notes |
|---|---|---|
| #24100 | Error Item Certify - specific items | |
| #24198 | Feature Group is not inherited | |
| #24280 | The record in table Azure Client already exists. Identification fields and values: Id='{3C5F3D53-B0BE-471A-B39C-D44762957CB1}' | |
| #24205 | Edit Allocation Tree missing action Features in Product Data menu | |
| #24263 | Track API response times | |
| #23915 | delete old records from table PIMX Publ. Line Change Log | |
| #23622 | Configuration package - mass update of values - Value %1 has been updated ... too many dialogs | |
| #23844 | Top level in publication line is not being translated when Channel assigned | |
| #23980 | Import Mapping - Invalid Destination Column ! | |
| #24080 | Update Publication / Update Publication Line doesn't update the price | |
| #24184 | API Feature: "The record in table Catalogue Feature Value already exists. |
Pimics PIM 9.1.7
Bugs
| Identification | Title | Notes |
|---|---|---|
| #24155 | Shopify: 401 "Unauthorized" (Invalid API key or access token) | {"errors":"[API] Invalid API key or access token (unrecognized login or wrong password)"} |
Pimics PIM 9.1.6
Bugs
| Identification | Title | Notes |
|---|---|---|
| #22417 | PIM Item Card doesn't contain action Features | |
| #23990 | Publication tree - add new line - The value of COPYSTR parameter 3 is outside of the permitted range. The current value is: -1. The permitted range is: from 0 to 2 147 483 647. | |
| #23538 | Publication Type "API Translation" missing value (field: Wert) in Publication Line | |
| #23605 | One feature can be added multiple times to Feature Group | |
| #22500 | Product feature - the same form names in the selection | |
| #23427 | Feature group in Product featuers - deleting of a structure line | |
| #23629 | Deepl: failer message | |
| #21204 | Catalog Group, Product Group, Chapter | User Story 21176: Excel Export Mapping - add Text, Product Group, Chapter to Source Type |
| #23913 | Publication API Translation - Catalog Feature not having right value translation |
Pimics PIM 9.1.5
Bugs
| Identification | Title | Notes |
|---|---|---|
| #23463 | Excel Export: Use Cell Value as Blob when necessary | |
| #23130 | Synchronize SharePoint report - own Refresh Metadata function and not hit OnAfterRefreshMetadata | |
| #22818 | Publication line - reorganization (translations missing) | |
| #23727 | Document for links resolved all as Type Enum Document & #23728: Public URL with docd doesn't seem to be working well | |
| #23572 | Inherit Feature Group: Duplicate Lines | |
| #23530 | Reference Card on Linking opens template and tries to create the card | |
| #23520 | Class Title remains inherited on children entity when class being removed from parent | |
| #23421 | Structure modification (9.2, hotfix 9.1) | |
| #23537 | Reorganisation for Feature Values longer then 250 is failing for Publication Types "Multilanguge Print" and "Multilanguge API" | |
| #23529 | Excel Mapping - the type NavBoolean is unknown | |
| #23656 | The record in table Azure Client already exists. Identification fields and values: Id='{76E172BE-B187-4A02-BFAF-C92F95E26D17}' | |
| #23329 | Error if a Value should be created through Product feature (9.2, hotfix 9.1) | |
| Avoid Duplicate Columns in Excel Mapping | User Story 12350: Create Excel Mapping and Export (to avoid: duplicate columns) | |
| #22485 | Export mapping Summit Trade- One Line per Item variant - Shows variant lines incorrectly | |
| #23493 | Checklist Relation - Reference is not checked | |
| #23448 | Excel mapping - Záznam v tabulce Zásobník aplikace Excel již existuje. Identifikační pole a hodnoty: Číslo řady='2',Číslo sloupce='115' |
Pimics PIM 9.1.4
Bugs
| Identification | Title | Notes |
|---|---|---|
| #23529 | Excel Mapping - the type NavBoolean is unknown | |
| #22485 | Export mapping - One Line per Item variant - Shows variant lines incorrectly |
Pimics PIM 9.1.3
Bugs
| Identification | Title | Notes |
|---|---|---|
| #23493 | Checklist Relation - Reference is not checked | |
| #23529 | Excel Mapping - the type NavBoolean is unknown | |
| #23564 | Other interface needs to use c6 | |
| #23129 | Domain is not set within "Pimics SharePoint File Synchronization" | |
| #23126 | Single Item or Single Item Group, attach data first to standard allocation, then references |
User Stories
In this version we have to change interface "PIMX Publication Update Line c5" to interface "PIMX Publication Update Line c6"
| Identification | Title | Notes |
|---|---|---|
| User Story 20350 | Shopify: Interface - call procedure when entity is reorganized | |
| User Story 23124 | Publication Group for References | #23454: Sister Item Group: Reference doesn't get reference to main sister, #23491: Function Type = Referencing |
Pimics PIM 9.1.2
Bugs
| Identification | Title | Notes |
|---|---|---|
| #23139 | New Line in Feature Group | |
| #23087 | Longer "Value ID" in Product Feature | |
| #23427 | Feature group in Product featuers - deleting of a structure line | |
| #23522 | PF - constant dialog - what to do with inherited lines on children - constant questions | |
| #23448 | Excel mapping - Záznam v tabulce Zásobník aplikace Excel již existuje. Identifikační pole a hodnoty : Číslo řady='2',Číslo sloupce='115' | |
| #22793 | PF - Inherited features from Class - Is Deleted = NO | |
| #23071 | Get Publick Link when Domain is empty | |
| #23129 | Domain is not set within "Pimics SharePoint File Synchronization" (cherry picked from commit 0775176b5b713a0ac9ccca58d2d5b8d292e95003) | |
| #23106 | RoleCenter: ChartPart PIMICS.ITEMSTATS leads to crash | |
| #23394 | Conflict in Application Area, Pimics User and GDAP | |
| #23062 | Default value set when Values were removed (9.2) | |
| #22868 | Feature can be added as a Value to itself (9.2, hotfix 9.1) | |
| #21251 | Export Mapping - fields added by modification are not exported | |
| #22815 | VC: Issue with calculating last used Line No. of Catalog Document |
User Stories
User Story 18629 | Excel Export: Item as table with feature per line
Pimics PIM 9.1.1
9.1.1 hasn't been released to AppSource. The bugs from it are included in a future release.
Pimics PIM 9.1
User Stories and Bugs
Pimics PIM 9.0
Features
360 page
Pimics has one page which shows all data in one place and gives a better overview for users. This page should be also editable and probably it should be based on our categories.
Product Features
The new way we work with features. We've redesigned the data structure to bring a more flexible way how users can handle features. It contains scenarios like inheriting from materials, skipping certain levels or just adding new possibilities like moving and grouping features, new types and even making features from another feature.
New Price List Experience
Pimics can work with the new price list experience defined by Microsoft.
Product Versions
It is possible to save versions of items, compare the data with older versions and eventually restore the data.
Variants
The concept of how we work with item variants has been redesigned to better fit users' requirements.
User Stories and Bugs
Pimics Vendor Catalog
(Top, Pimics PIM, Pimics Vendor Catalog, Pimics on-premise, BMECat for Pimics)
Pimics Vendor Catalog 9.1.2
Bugs
| Identification | Title | Notes |
|---|---|---|
| #25191 | Trigger for procedure Set end date of existing prices | The new even has been published for the activation process |
Pimics Vendor Catalog 9.1.1
Bugs
| Identification | Title | Notes |
|---|---|---|
| #24523 | German translation of progress label is missing placeholder for percentage | |
| #24505 | Import of Import Mapping fails if Transf. Params are defined | |
| #24755 | Length of Vendor Feature.Value < Product Feature.Value | |
| #24128 | Item activation - EAN not included | |
| #24010 | Modificaton of the Destination field in "PIMX Excel Mapping Line" (Excel mapping) |
Pimics Vendor Catalog 9.1
Bugs
| Identification | Title | Notes |
|---|---|---|
| #20891 | Vendor Feature List - value of "Applies-to Type" field is incorrectly displayed | |
| #21694 | Catalog Setup - Install needs to install alsoBMECat + Vendor Catalog | |
| #20577 | Vendor Catalog is not functional | |
| #22047 | Vendor Item - Mismatch on Item Vendor - refering to non-existing items + activation made against another item | |
| #21390 | Default Language Code blank; run VC Import on background; no error | |
| #21693 | AutoTest: FeatureNotInClass | |
| #21692 | AutoTest: ValueNotInFeature | |
| #23693 | Build fails because of File Repo and Unit Conversion references | |
| #23823 | XML export mapping - Home / Export mapping | |
| #23481 | Missing information after price activation | |
| #23170 | Vendor Feature - Checklist - Product Feature issue | |
| #22662 | Validate Vendor No. when Activation items |
New Functions
| Identification | Title | Notes |
|---|---|---|
| User Story 22688 | Map existing Documents on external IDs | |
| User Story 20821 | Import of BMECat using different ETIM versions |
BMECat for Pimics
(Top, Pimics PIM, Pimics Vendor Catalog, Pimics on-premise, BMECat for Pimics)
BMECat for Pimics 9.1
Bugs
| Identification | Title | Notes |
|---|---|---|
| #18491 | Vendor Item fields have wrong type to be compatible with BMECat specification | |
| #20879 | Check if we delete records from BMECat File table when the import is deleted | |
| #20908 | Import from BMECat - counter goes from 0-50 (and 50 means 100 percent imported), while it should go 0-100 | |
| #21323 | Vendor Catalog - Import Log missing identification of Import No. | |
| #21385 | BMECat Value 0.1 cannot be evaluated for type Integer. | |
| #21691 | AutoTest: ClassHasBeenDeleted | |
| #21692 | AutoTest: ValueNotInFeature | |
| #21693 | AutoTest: FeatureNotInClass | |
| #21694 | Catalog Setup - Install needs to install alsoBMECat + Vendor Catalog | |
| #22127 | Update Item Reference inconsistency - Import vs action on the list | |
| #22183 | Import UDX Mime ETIM under PIMXBeta | |
| #22478 | BMECat - Do not set Activated when the entity is Certified | User Story 12298: Find Vendor Item in existing (Catalog) Items |
User Stories
| Identification | Title | Notes |
|---|---|---|
| User Story 20821 | Import of BMECat using different ETIM versions |
Pimics on-premise
Pimics on-premise 9.1
Removed .net packages
Pimics contains only the system .net packages and all our custom packages have been removed. Please, see the installation guide if you have any issues.
Pimics on-premise 9.0
No changes in this version. It has been aligned with other extensions and Business Central 23.
See Also