Finance | Project Operations, Human Resources, ...

How to show display method fields on workflow configuration?

(0) Share

Report

Posted on by bilal170795

185

Hi I am created a workflow for sales order (Custom workflow) which I have created successfully, now I am configuring my workflow and I have to use the field Estimated Margin% in the conditional statement of workflow configuration as shown in the below screenshot

I am using a query that is returning all the SalesTable and SalesLine fields except the fields that are using the display method and this estimated margin is also a display method(OOB) created in form datasource as shown in the below screenshot

How can I get this field in workflow configuration, Thanks.

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Suggested answer

Martin Dráb 239,082 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

You can add methods to the workflow document class.

For example, look at parmCalcTotalMiscCharges() in PurchTableDocument class.

Was this reply helpful? Yes No
bilal170795 185 on at

Like (0)

Report
Copy link

Link copied!
Hi Martin,

Thanks for the response, I tried to add my field in a similar manner but am still unable to see my field maybe it will come with the different name I am sharing my code and the area where I am trying to find my field, so you can have a better insight

class XYZ_SalesTableWorkflowTypeDocument extends WorkflowDocument { SalesTable salesTable; SalesLine salesLine; ///
/// Returns query name for the workflow document. ///
/// /// Name of the query XYZ_SalesTable. /// public queryName getQueryName() { return querystr(XYZ_SalesTable); } public Percent MarginPercentStr(CompanyId _companyId, TableId _tableId, RecId _recId) { Percent margin; salesTable = this.getSalesTable(_recId); select salesLine where salesLine.SalesId == salesTable.SalesId; margin = salesLine.McrMarginPercent; return margin; } private SalesTable getSalesTable(RecId _recId) { if (!salesTable) { salesTable = salesTable::findRecId(_recId); } return salesTable; } }

Was this reply helpful? Yes No
Martin Dráb 239,082 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Try respecting the naming convention - call the method parmMarginPercentStr() instead of MarginPercentStr().

I'm not sure if it'll make a difference, but I have a feeling that the framework really looks just for methods prefixed with "parm".

By the way, are you sure that you want to use a value from a SalesLine without specifying which one? You leave the selection to the database server and if not all lines have exactly the same value of McrMarginPercent, you can't be sure which one you'll get. It looks like a bad design to me. I would look again at the actual business requirement...

Was this reply helpful? Yes No
bilal170795 185 on at

Like (0)

Report
Copy link

Link copied!

Hi Martin,

Thanks for pointing out yes you are right about SalesLine value. So I would like to give more brief details about the business requirement that I am configuring the workflow and in this workflow, I have to put some conditional statements on the basis of the values of Estimated margin% but when I am looking it in the list of field I am unable to find it, the list I show you in the previous post. Moreover, I would like to tell you what I found while digging is that my datasource in query has the value of MCRMarginPercent(i.e; Estimated margin) but the list is not showing the respective field, previously I thought it could be due to the reason of display method but this field exist in the database.

Was this reply helpful? Yes No
Martin Dráb 239,082 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Do you realize that the workflow document you're using is about the whole order, but field isn't on purchase order header (PurchTable)? It's on the line (PurchLine). You either need a value aggrgated for all lines lines, or you need to use a line-level workflow. It depends on business requirements; unfortunately your description above doesn't cover this topic.

Was this reply helpful? Yes No