web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Supply chain | Supply Chain Management, Commerce
Unanswered

eCommerce Extensibility: What to extend to achieve presented scenario?

(1) ShareShare
ReportReport
Posted on by 289

Hello all,

I am seeking some guidance regarding a specific scenario/use case need from a client. I will do my best to detail the scenario below, capture my understanding of what needs to be accomplished to provide such functionality, and am seeking guidance/clarification on what I'm missing. The client has just the Online Store, there is no brick-and-mortar store, so this scenario/inquiry will relate specifically to online store functionality, the SDK where modules can be customized, and the RetailSDK.

Scenario:

  • User places order on website. 
  • User navigates to order history.
  • User navigates to order details of specific order.
  • User clicks button added to the Order Details module that calls an API and gets back a String.
  • The String is stored in a Sales Order Attribute.
  • If the User later clicks the same button, the code stored in the Sales Order Attribute is called and displayed to the User.

Sales Order Attributes:

  • I understand that order attributes must be defined and assigned to the channel in HQ. This step is completed. To achieve this, we followed the below documentation.
  • There is an attribute set at the sales line level that can store a string of text.
  • I want to extend the attribute to add business logic at the website level of the online store to interact with this attribute field.
  • We will be running a function on a button on the order details page to handle the API call and parse the response at the website level.
  • I want to store the parsed string response in this sales order attribute.
  • Future button clicks on the order details page will check if the attribute field is empty.
  • If the attribute field is not empty, the value held is returned.
  • If the attribute field is empty, the button will run its API call and response parsing logic.

If I can offer any clarification, please let me know. If my understanding is completely off and to achieve our desired functionality extending the CRT is not the direction to take, any feedback pointing me in the correct direction would be greatly appreciated.

Thanks,

Josh R.

I have the same question (0)
  • Jritz Profile Picture
    289 on at

    Bumping for visibility. Still looking for feedback on the above. Reading more into data actions, does anyone think we could achieve the above with data actions alone?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Supply chain | Supply Chain Management, Commerce

#1
Mallesh Deshapaga Profile Picture

Mallesh Deshapaga 296

#2
Laurens vd Tang Profile Picture

Laurens vd Tang 234 Super User 2026 Season 1

#3
Syed Haris Shah Profile Picture

Syed Haris Shah 139 Super User 2026 Season 1

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans