-
Type: Story
-
Status: Closed (View Workflow)
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Sprint:2021.R3 New Features Sprint 1
-
SCRUM Team:Brotherhood of Mutants
-
Story Points:2
-
Work Type Classification:Sustaining
Story
As an admin, I would like the UOM import to support specials characters.
Details
It's possible that some text strings delivered in the UOM import may include special characters like the ones below. We need to specifically confirm that the Unit of Measure data can process and accept these characters.
- á
- Á
- é
- É
- í
- Í
- ó
- Ó
Documentation for I4 process: https://cfacorp.atlassian.net/l/c/sVRQFVwZ
- VI Import: https://cfacorp.atlassian.net/l/c/nhJkYNqX
- For example: PruchaseUnit has the following directives,
{UpdateVendorEntityItem}
{DefaultToReportingUnit}
{UpdateFromItem}
{AddUOMMapping}, does this process create a UOM, or does it work with the {AddUOMMapping}
directive when using Spanish characters
- IN-VendorItemImport-220221-1408.pdf
- For example: PruchaseUnit has the following directives,
{UpdateVendorEntityItem}
{DefaultToReportingUnit}
{UpdateFromItem}
{AddUOMMapping}, does this process create a UOM, or does it work with the {AddUOMMapping}
AC
Confirm in the UOM Field
- When a text string in the UOM field of the UOM import includes special character the import is successful and the UOM is populated correctly in the UI.
- Clones
-
CFAMX-13212 Localization: Update Vendor Item Import to Support Special Characters
- Closed
- implements
-
CFAMX-11800 All - INTL - Support special characters in Imports/Exports
- Closed
- Is Clone Of
-
CFAMX-13222 Localization: Update Item Import to Support Special Characters
- Closed
- relates to
-
CFAMX-14571 (CFA TEST) UOM Import Converts Special Characters to Question Marks in Database
- Done