Supply chain | Supply Chain Management, Commerce

Punchout cXML and extrinsic values

(5) Share

Report

Posted on by HNd365FO

152

I am a business with multiple locations. Each location orders products individually but they all share the same vendor(s). When the user at each location visits the vendors shopping platform to order goods they can only see items allowed for their respective location (ie. customized catalog for each location).

I am being asked to send an extrinsic value along with my cXML request when punching out to uniquely identify which location is doing the ordering.

How do I send a unique username and location code as an extrinsic value in the request if we only have one instance of D365?

How do I make the extrinsic value dynamic in the request based on the user/location that's punching out?

Categories:

Dynamics 365 Supply Chain Management

I have the same question (0)

All responses (7)

Answers (0)

Guy Terry 28,866 Moderator on at

Like (0)

Report

Punchout cXML and extrinsic values

You could ask your Vendor to provide different PunchOut credentials for each of your locations.

In F&O, you could configure an External catalog for each location.

Was this reply helpful? Yes No
HNd365FO 152 on at

Like (0)

Report

Punchout cXML and extrinsic values

Thanks for your response, Guy.

Could you expand on this multiple external catalogs suggestion? I am not sure what you mean and how it could be implemented.

I truly appreciate the help.

Was this reply helpful? Yes No
Guy Terry 28,866 Moderator on at

Like (0)

Report

Punchout cXML and extrinsic values

This is the list of extrinsics that F&O supports. If you can't use one of these I think you'd need to be doing a development.

Have you considered asking the Vendor if they can do a different PunchOut website for each of your locations, and configuring multiple External catalogs?

Was this reply helpful? Yes No
HNd365FO 152 on at

Like (0)

Report

Punchout cXML and extrinsic values

bumping this up again. I am still trying to figure this out.

Has anyone actually done this?

Was this reply helpful? Yes No
Guy Terry 28,866 Moderator on at

Like (0)

Report

Punchout cXML and extrinsic values

Username is a supported extrinsic, but unless each of your locations are different Legal entities in F&O, there is no 'location' extrinsic.

Perhaps you could provide the vendor with a list of users and their default location, and the vendor could build appropriate logic on their end.

Was this reply helpful? Yes No
Jonas "Jones" Melgaard 4,855 Super User 2025 Season 2 on at

Like (0)

Report

Punchout cXML and extrinsic values

You have the ability to send the WHS UserName, but I wonder if it's enough for you?
It's documented here: https://learn.microsoft.com/en-us/dynamics365/supply-chain/procurement/purchasing-cxml-enhancements

I'd say that it's worth investigating if a customization can solve this.

Was this reply helpful? Yes No
Suggested answer

Holly Huffman 6,520 Super User 2025 Season 2 on at

Like (0)

Report
Punchout cXML and extrinsic values

Good morning, afternoon, or evening depending on your location!

You can dynamically send extrinsic values (such as username and location code) in your cXML PunchOut request by configuring external catalog settings in Dynamics 365 Supply Chain Management.

How to Send a Unique Username & Location Code in cXML

Use cXML Parameters in External Catalog Setup

Go to Procurement and Sourcing > Setup > cXML Management > cXML Parameters.

Configure extrinsic values to include user-specific and location-specific identifiers.

Modify the PunchOut Request Format

In Procurement and Sourcing > External Catalogs, define Order Properties to include dynamic extrinsic values.

Ensure the cXML request template includes placeholders for username and location.

Make Extrinsic Values Dynamic Based on User/Location

Use user attributes in D365 to dynamically populate extrinsic values.

Configure security roles or user profiles to store location codes.

Implement Power Automate or X++ logic to inject the correct values into the cXML request.

Validate the Request Setup

Test the configuration using the Validate Settings action in the external catalog setup.

Ensure the vendor receives the correct extrinsic values in the PunchOut request.

Please note: I teamed up with CoPilot AI to research and craft the best response to your question!
Hope this helps some!

Was this reply helpful? Yes No