Possible Bug in Inventory Import
Posted: Fri Mar 05, 2021 2:06 pm
I believe given we have a customer who has an issue created by this, that there is no validation of custom fields in the inventory import, by this I mean we have ended up with text in a numeric field.
This then has caused a custom view that casts what it expects to be a number to a numeric to fall over.
On a quick look through the code from the import screen it would appear when you delve into the object that the sets custom field is as follows and then the custom field value never checks back to the custom field's type
Am I correct in my understanding of this as I'll log it as a bug through the service desk if it is?
This then has caused a custom view that casts what it expects to be a number to a numeric to fall over.
On a quick look through the code from the import screen it would appear when you delve into the object that the sets custom field is as follows and then the custom field value never checks back to the custom field's type
Am I correct in my understanding of this as I'll log it as a bug through the service desk if it is?
- Code: Select all
private void SetCustomField(ref Inventory Inventory, string Value, string RowData, string[] Row, int RowNo, Mapping Mapping)
{
CustomFieldValue value2 = Inventory.CustomFieldValues.get_ItemFromSettingName(Mapping.DestinationProperty.RecID);
if (value2 > null)
{
value2.Contents = Value;
}
}