DXC Item Creation Wizard
DXC Item Creation Wizard - Release notes
DXC Item Creation Wizard - Release notes
With effect from October 31st, 2025, we have chosen to discontinue the option of continuing maintenance for our solution, “Item Creation (ICW) for Dynamics 365 Finance and Operations.”
The final release of the product will occur on October 31st, 2025, which is twelve months from now. We will give you the source code so you can keep using it, but you will be responsible for maintaining it after that. Alternatively, you can raise a T&M work order with DXC Customer Services if you’d like ongoing support.
To ensure that you have time to find a replacement product if needed, DXC will continue providing bug fixes for the next 6 months.
This document describes the features that are either new or changed in the release version mentioned.
DXC Item creation wizard 10.0.34.20231004 runs on the following Microsoft releases
Release date: 4th October 2023
Bug fixes
| Number | Name | Description |
|---|---|---|
| 15941 | During the manual update session, attributes are reset to “default” | When changing attributes against a released product all attribute values would previously be reset to the default value listed in the item creation template. The creation designer’s provided product attributes will not change unless a value is entered into the relevant field. If the field is left blank or unchanged the value will not update. See New Feature 16016 below for specifics on how the attribute fields in the creation designer look after processing an update. |
| 16021 | Production fields do not update when the Production Type is updated to Formula. | When processing an update template to set the “Production Type” field to the value of Formula, while also incorporating changes to values in Production Group, Production Pool (all located under the Engineer tab) and Coverage Group (located under the planning Tab), the Production Type field would update to the value of Formula however the other fields would not update. Field values would display correctly in the Item Creation Designer (as per below if processing via UI) however would not process through to target. |
This would occur during upload and via the user interface without warning or error being issued.
New features
| Number | Name | Description |
|---|---|---|
| 16016 | Display Active product attribute | Users now have visibility of what the active product attribute value is via the new field, active product attribute value. Users continue to have the ability to update the attribute value from within the designer. |
There is no impact on the existing process to update product attributes or Template Creation. The Change simply increases visibility from within the User Interface.
Release date: 23 June 2023
Bug fixes
| Number | Name | Description |
|---|---|---|
| 14020 | Product attribute values default back when 2 templates are submitted | Previously when 2 or more templates are submitted into workflow at the same time the product attributes will automatically default back to the state before any changes were submitted, even if the 2nd template does not contain attributes. Attributes now only change if the template contains attributes. |
| 14639 | All attributes display system default status when running a manual update session | If attributes are included as part of a manual update session, the values of the attributes displayed are those at the start of the session. The exception is where attributes have default values as part of the template, then the template “default” value is now displayed in the update session. |
| 10869 | ProductionType does not update to value ‘Formula’ | ProductionType can be updated to ‘Formula’ simultaneously as other fields on the item |
Release date: 15 June 2023
New features
| Number | Functionality | Reason |
|---|---|---|
| 14020 | DXC License | DXC License version 10.0.34.202306151 |
| Number | Functionality | Reason |
|---|---|---|
| N/A | License manager | License manager version 10.8.32.10171 Enhanced Licensing capabilities to assist with licensing support and scaling. Note: Required to upgrade all installed DXC products to at least the following versions: • EDI 10.0.29.202305053 • Finance utilities 10.0.29.202305051 • SmartSend 10.0.29.202304142 • Core extensions 10.0.29.202304142 • DocuSign 10.0.29.202304211 • Item creation 10.0.29.202304211 • PLM 10.0.29.202304211 • Forex 10.0.29.202305101  |
| Number | Functionality | Reason |
|---|---|---|
| 8335 | Status Data Entities | Data entities for the following tables have been included * DXCICStatusTable * DXCICStatusTransitionRule * DXCICStatusAutoRuleTable |
| 9192 | Item creation import sessions | The import sessions form will no longer display by default records with a status of Completed, Rejected or Cancelled. The visibility of these records can be toggled using the Show closed control. When the import session form is opened the latest record will be selected. |
| 9746 | Item Creation list page | The item creation list page form will no longer display by default records with a status of Completed, Rejected or Cancelled. The visibility of these records can be toggled using the Show closed control. |
| 9748 | Item status, released product variants | The current item status for a product variant is now displayed within the release product variant form. |
| 9786 | Create DXCICStatusItemTable record on variant creation | When a product variant is created from a creation template, the variant will inherit the items status defined on the template. |
| 9926 | Item status - block inventory transactions | A new transaction type is available for blocking by using item statuses. The new option Inventory will enable the prevention of product or variants with the item status from being included in; * Inventory movement * Inventory adjustment * Inventory transfer * Inventory count |
Bug fixes
| Number | Name | Description |
|---|---|---|
| 9510 | Import workflow, Auto reject creates loop | If the workflow element Approve item creation import is set to reject the import session, the rejected import session would be resubmitted. The import session status is now correctly updated to rejected. |
Bug fixes
| Number | Name | Description |
|---|---|---|
| 9569 | Field does not exist in table | Where an attribute field is included within the same file mask as values from the product translation table the field was included in the updated validation for 9504. |
Bug fixes
| Number | Name | Description |
|---|---|---|
| 9504 | Update file is blanking out fields | Tables without a reference to the ItemId or an inventory dimension field were found to clear the contents of a field if the field was included in an imported file without a defined value. Where a field in included in the template and no value is provided, the designer now displays the pre-existing value for the matching record. |
| Number | Functionality | Reason |
|---|---|---|
| 6232 | Validation on failed import session | Imported files that have failed validation can now be revalidated from within the import session designer using the same validation applied on import. |
| 9192 | Delete a cancelled import session | The deletion of import sessions that have been submitted to workflow and recalled can now also be deleted from the import session table. Doing so will also remove the item creation records associated with the import session. |
Bug fixes
| Number | Name | Description |
|---|---|---|
| 9174 | Financial dimension defaults | Default values set on item creation templates for financial dimensions are now being applied to the item. Where an alternative value is provided in the imported data, this will be used instead. |
| 9175 | Approved vendor writing to target table prior to workflow completion | A new table (DXCICCreationPdsApprovedVendorListTable) has been created to stage imported values during the workflow process, as the table structure is not compatible with the use of a TempDB. Templates that reference the previous Approved Vendor table will need to be updated to reference the value. |
| 9202 | Import validation against multiple companies | Where import session lines are created for each company on the template header, a distinct validation will be for each record based on values appropriate for each company. |
| 9215 | Import validation not completed on certain fields | Fields that were not validating on import are now validated and a log provided to identify the incorrect value that has been imported. |
Bug fixes
| Number | Name | Description |
|---|---|---|
| 6264 | Financial dimension | Imported financial dimensions were not validated against existing values. The user was not provided with a validation error or log when a value was unable to be imported. Validation errors and log are now present when a financial dimension cannot be written to the designer. |
| Number | Functionality | Reason |
|---|---|---|
| 8412 | Import validation | When importing a file, additional validation is now run on imported string and enum fields to confirm that the value being imported exists. Where validation tables are specific to a company/DataAreaId the validation is completed on records that match the company on the item creation template header, as defined by the user. Note: Additional validation is not supported for integer and date field types. Note: Additional validation is not currently supported for attribute values. |
Bug fixes
| Number | Name | Description |
|---|---|---|
| 8402 | Clear financial dimensions | The Clear field value defined on the item creation template header allows for a field to be updated to a blank value when specified character/s are included in an import file. When used on a financial dimension field the existing financial dimension value was not being cleared. This is now supported. |
| 8394 | Update alternative item number | When importing a value into the field Alternative item number the value in the mapped field of the import file was not used. |
| Number | Functionality | Reason |
|---|---|---|
| 7865 | Feature Management | Move licensing to License Manager and Feature Management. |
| Number | Functionality | Reason |
|---|---|---|
| 8344 | MCRInventTable | Change to extended data type (DXCICItemId) on MCRInventDim to improve the query. |
| Number | Functionality | Reason |
|---|---|---|
| 8221 | Update template, status | Leaving the status on an update template blank will no longer trigger an update of the item status. The existing item status for the updated product will now be retained. |
Bug fixes
| Number | Name | Description |
|---|---|---|
| 8254 | Generate variants automatically | When marking the field Generate Variants Automatically in a creation template a validation is run to confirm the subtype is Product Master. This validation failed, preventing the record from being submitted to workflow. |
| 8274 | Attribute values not recorded for all supplemental hierarchies | Attribute groups assigned to nodes in a category hierarchy of type Supplemental retail hierarchy allow for entry of attribute values using the Item Creation designer. This only works for the first hierarchy of this type, subsequent supplemental hierarchies do not return the attributes, preventing the value from being recorded on the product. |
| 8334 | Update alternative item number | A template with an assigned team can be seen by all users, so long as the template is active. |
| Number | Functionality | Reason |
|---|---|---|
| 8070 | New table | New table Product relationships (EcoResProductRelationTable) available for use in templates. |
| Number | Functionality | Reason |
|---|---|---|
| 8083 | Data entity addition | Entity: Item status link Staging table: DXCICStatusItemStaging Target entity: DXCICStatusItemEntity |
| Number | Functionality | Reason |
|---|---|---|
| 8028 | Security enhancements | Creation of two distinct security roles Item creation clerk – Item creation user, able to initiate or update an item creation record. View and manage imported files Item creation manager – module admin, can update parameters relating to Item creation and create/edit Item creation templates. Security privilege added where not available Parameters form Export template (Template steps) Creation import files form Create workflow |
| 4808 | Data entities | New data entity added for the parameters table. |
| 8033 | New tables | New tables are available for use in templates; Approved vendor (PdsApprovedVendorList) Direct delivery (MCRInventTable) |
| 7690 | Creation import session | Template version used for import can now be viewed without having to navigate to line view A filtered view of creation import sessions showing only records assigned to the user has been added. |
| 7942 | Formatting changes | Replaced references to PLM with Item creation Indented submenus within the setup section |
Bug fixes
| Number | Name | Description |
|---|---|---|
| 7909 | Default order setting – Site | The field Site was unavailable for selection in the item creation template for the template table Inventory dimensions (Site-specific purchase order settings - Default) but could be applied manually. The field was added to the list for selection. |
| 7931 | Changes to an assigned team not reflected | When changing the assigned team on an Item creation template it does not update the visibility of the template for either the new or removed team members. |
| 7903 | Creation import files – Active | Only activated template versions should be visible within the list of templates on the Creation import files form |
| 7449 | Reservation hierarchy | Field was unavailable for editing within the designer and could only be populated as a default |
To align with MS best practice and to protect our IP the following applies to the release process.
Depending on the installation history follow one of these guides to install the new release.
If you’re installing the new release in an installation that already has a previous version of the product installed and you’re not using it for debugging or extension. We recommend that you;
If you’re using our model source code for extension or debugging and would like to continue using it, please do the following to apply the new release with the source code.
If you don’t follow these instructions and continue building your installation deployable package using the license model source code, the installation will continue using the same license model as before applying the release.