Required Attributes for All Publication to McLane

[CommunityJedi22]

1WolrdSync recently turned on derivation so that these attributes are now required for all GTINs when you publish to McLane.  This is true whether you have the McLane playlist enabled in IM or not.  If using IM to publish to McLane, please add the playlist and these attributes will be aggregated for you with the validations in place.

Below is a text version so you can copy the XML attribute names as needed:  

PLAYLIST M/O?	PL Name	New/Existing	XML Name
Mandatory	mclane_GROCERY	Existing	allergenRelatedInformation/isAllergenRelevantDataProvided
Required	mclane_GROCERY	Existing	countryOfOrigin/countryCode
Mandatory	mclane_GROCERY	Existing	grossWeight
Required	mclane_GROCERY	Existing	innerPack
Required	mclane_GROCERY	Existing	manufacturer/gln
Required	mclane_GROCERY	Existing	manufacturer/name
Mandatory	mclane_GROCERY	Existing	marketingMessage/sequenceNumber
Mandatory	mclane_GROCERY	Existing	marketingMessage/tradeItemMarketingMessage
Mandatory	mclane_GROCERY	Existing	netWeight
Mandatory	mclane_GROCERY	Existing	productDescription
Required	mclane_GROCERY	Existing	quantityOfNextLevelWithinInnerPack
Mandatory	mclane_GROCERY	Existing	shortDescription
Mandatory	mclane_GROCERY	Existing	tradeItemFeatureBenefit/featureBenefit
Mandatory	mclane_GROCERY	Existing	isPackagingLabelledWithDrugFacts

 This is a screen capture of the required attributes from our attribute requirements doc for the derivation: 

[Dfturner]

Was there a notice from McLane on this? We have been unable to publish products to McLane since derivation was turned on, even though validation returns warnings only.

[ShananWalker]

We are running into the same issue and not able to publish any items to Mclane! We did not receive any notification of this being implemented from Mclane and we are not currently sending many of these required attributes.

Is there any inclination of this being reversed?

[CommunityJedi22]

Hello and thank you for reaching out regarding this impactful issue.  Yes, there are discussions about relaxing some of the more impactful validations but that action has not been acted upon yet.  I can add more updates here as we learn more about any future changes to these validations.

[CommunityJedi22]

We have an update on the McLane validations from our Product team.  

The source of the issue is some rules in their Playlists calling for some attributes to be mandatory. The activation of derivation forces the population of these attributes at all levels of the hierarchy. Some of the attributes are really more relevant for specific levels of the hierarchy and not others.

The solution will be that this coming weekend, March 6, 2021, we will be turning off derivation for McLane in the Production environment while we work to adjust the validation rules. We will be working with McLane next week on what those rules should look like.

Once those new requirements are completed, we will be deploying them to Preproduction (timing TBD). Once in Preproduction, we will work with a few suppliers for testing to ensure they function as needed. Once testing is successful and approved, we will then schedule the new rules to be moved into Production and derivation to be restarted.