EPiServer.Commerce.Core.13.24.0 LongString MetaDataType adds nvar

EPiServer.Commerce.Core.13.24.0 LongString MetaDataType adds nvarchar(1) column in the meta class database table

Reimond Checiches

Vote:

We worked on Payment Connector and created XML files for the custom payment meta class import. Two of the fields of the imported metaclass have a type of LongString. Please see the below meta field definition for details:

<MetaField>
    <Namespace>Mediachase.Commerce.Orders</Namespace>
    <Name>CyberSourceGooglePayData</Name>
    <FriendlyName>CyberSource Google Pay Data</FriendlyName>
    <Description>CyberSource Google Pay Data</Description>
    <DataType>LongString</DataType>
    <Length>8000</Length>
    <AllowNulls>True</AllowNulls>
    <SaveHistory>False</SaveHistory>
    <AllowSearch>False</AllowSearch>
    <MultiLanguageValue>False</MultiLanguageValue>
    <IsSystem>False</IsSystem>
    <Tag></Tag>
    <Attributes>
      <Attribute>
        <Key>useincomparing</Key>
        <Value>False</Value>
      </Attribute>
    </Attributes>
    <OwnerMetaClass>CyberSourceGooglePayPayment</OwnerMetaClass>
</MetaField>

The above-described meta field is created in the database as a column with type nvarchar(1) using EPiServer.Commerce.Core.13.24.0, while on EPiServer.Commerce.Core.13.20.0, the same meta field is created as ntext type, using the same XML for the metaclass and meta fields import.

I did not found any release notes related to the metadata type changes. Since in EPiServer.Commerce.Core.13.20.0 the old types are available, the changes to the metadata types were applied in one of the versions between 13.20.0 and 13.24.0.

LongString metadata type mapping in EPiServer.Commerce.Core.13.20.0:

LongString metadata type mapping in EPiServer.Commerce.Core.13.24.0:

Are these changes final ones? If so, what type of metadata do you recommend to use instead of the old LongString type which mapped to ntext SQL data type?

#228196

Sep 21, 2020 8:15

Quan Mai

Vote:

I believe it's -1 which basically means nvarchar(max). ntext is a deprecated type, so moving to nvarchar would be the right thing to move for future proof

#228234

Sep 21, 2020 21:52

Reimond Checiches

Vote:

Unfortunately, LongString is created in the database as nvarchar(1), not nvarchar(max), so at this point, LongString metadata type cannot be used.

#228259

Sep 22, 2020 8:22

Quan Mai

Vote:

That is strange. I will ask Commerce team to look into this.

#228260

Sep 22, 2020 8:32

Sergey Matyunin

Vote:

We have got the same issue on version 13.23.1

Please, fix asap.

#228546

Sep 29, 2020 9:12

Quan Mai

Vote:

This bug is fixed with high priority and will be released in 13.25.0

Thank you for your patience and apologies for the problems it might have caused.

#228547

Sep 29, 2020 9:16

Sergey Matyunin

Vote:

@Quan Mai: Could you clarify the date when the new release is expected, please?

#228895

Oct 05, 2020 6:35

Quan Mai

Vote:

It should be out this week, if nothing extraordinary happens. However that'd be a QA decision and I have no influence over that.

#228899

Oct 05, 2020 8:05

Quan Mai

Vote:

13.25 is now released - please upgrade to have this issue fixed

#229131

Oct 08, 2020 7:11