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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Service | Customer Service, Contact Center, Fie...
Suggested Answer

Custom Fields on Products (plus how to get them to Opportunity Lines, Work Order Products, Customer Assets)

(0) ShareShare
ReportReport
Posted on by 390

We have a few custom fields like (System, Phase, Room Installed) that contextually don't apply to the Product table since it will be different data on the product per install.

So we started by adding the fields to the Opportunity Line table (OpportunityProduct).

We'll use the Phase information on the Work Order in the future mostly.
The System and Room Installed will need to pass through for storage with the Asset and creating that Location if not already.

OPTIONS

1.  I assume I can create custom fields for each of the tables and then use calculated fields or some other method.

2.  I could create a new Entity and create a 1:N relationship to Product that would flow throughout the entire use of Products in FS365.

QUESTIONS

Pros/Cons of each above?
Better options than above?

I have the same question (0)
  • Suggested answer
    antc Profile Picture
    2,909 on at

    I kind of understand where you are heading, are you thinking of using Customer Assets for Work Orders?

    You could definitely create a custom table and link to Opportunity Product and on closure of Opportunity run a Flow that links the custom table to the Customer Asset or other Table that you plan to base your work orders off.

    I have used javascript, plugins and Flow's to copy columns from Product to Opportunity Product with Flow being the easiest method and as you are aware you need to add the fields to the Product as well as Opportunity Product.

    Without knowing your actual requirements it may be reasonable to store the columns (fields) on the Opportunity Product table or a custom table. You will find it easier to create Flows from columns on one table vs a related child table as it will require and extra request in a flow or code.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Service | Customer Service, Contact Center, Field Service, Guides

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 61 Super User 2025 Season 2

#2
Siv Sagar Profile Picture

Siv Sagar 52 Super User 2025 Season 2

#3
Daniyal Khaleel Profile Picture

Daniyal Khaleel 31 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans