Best Of

@Paul Salkeld Just a thought.... leverage what might work for you to avoid scripting.

Workflows are great when your action/conditions are on the header record.

Are your Sales Orders transformed from Estimates/Quotations or entered manually & not tied to an Estimate/Quotation?

Could you consider having two forms and save the transaction with the form?

1. Form 1 with Class X on the header(main) and Billing Schedule hidden on the lines
2. Form 2 with Class Y on the header(main) and Billing Schedule Show on the line

You can evaluate the Quotation header Class and upon transformation to the Sales Order, set the Sales Order form to the appropriate form.

If Sales Orders are manually created, you could try a workflow that would deliver a pop up warning message on create, asking if the Class will be X and suggest, then select Form 1.

A second check on Class could execute & would be annoying when people got it wrong. Have the workflow change the form when the Class value is X. (this is annoying because the form will be switched and all entered data will have to be re-entered, but it will only happen until it becomes habit).

You will determine your volume & how big an issue it is today to decide whether a script is warranted or a workflow will do.

Best regards,

Hi @Vernita,

Good day! As you can see on the left side there is a view filter there which default was selected. As per my experience you can customize the view and there assign the results and filters you will apply. Also further clicking the buton more options during customizing view will give you like saved search form with the criteria to further limit the transactions that will appear into the type you like. However, these approach is on a per user setting only. Meaning if you will apply to all users, need to change the viewing they have one by one.

Hope this helps. Thanks!

Best regards,

Emil

Just so it is in this thread.

I've experienced slowness as well & did create a Case #4743120: Performance since Account Move to OCI.

I have been receiving updates. No resolution date. No action necessary here, just posting to demonstrate, not alone. ?

@Mikko De La Fuente-Oracle Yes it was visible. I was able to find the solution though.

The correct code is:

{{record:salesorder:{{state:dataRecord:scriptParams:transactionInternalId}},item:line:{{state:dataRecord:scriptParams:transactionLineId}}-custcol_fulfillment_group_id}}

The problem is that I had a space after the comma before item:line.

Thanks for your help!

I think currency reval generates each month and reverses each month but on every transaction in the database.

Take a look at the Suite Answer ID: 82643 as a start and all the related links at the bottom of this one.

SuiteAnswer ID: 14964

Suite Answer ID: 14971

Hi @Dallas H,

Good day! As per checking your file, if you noticed on the external ID field, those with the same external ID were not lined up consecutively, thus resulting the system to finish creating the transaction record when it detects another external ID. For example the first two lines external ID is 5769 then the third line is 1264863. When the system sees the 3rd line, it will assume that the transaction record with external ID 5769 is already finished and complete it. So when another line has the same external ID, the system will result in an error and notify you that a transaction record were already saved under that external ID.

For remedy on this one, you can reupload again but not as new in the upload type but under update. So that it will update those already created transaction record.

Hope this helps. Thanks!

Best regards,

Emil

Hi @Dallas H,

Good thing it worked, maybe the update need something else for the mapping. Anyway, usually for the Account since you are doing vendor bill, it seems it is asking for the AP Account? Did you check those vendors if you have assigned a default AP account? But it seems from your file you assigned the account with the Internal ID. So if it is okay with other accounts, it should have no problems. Maybe need to check the vendor and the account record to review possibility on the errors.

Hope it somehow helps. Thanks!

Best regards,

Emil

Okay it turns out I was just making it more complicated than it need to be, answer was:

CASE WHEN ({type} = 'Sales Credit' AND {createdfrom.trandate} < '01/07/2022') THEN {custcol_pct_titan_cost} ELSE NULL END

Hi @KNason76,

I also have the same dilemma before. What I did was create a custom body field (decimal number format), then apply to the form. After that I created a workflow for the transaction for getting the value from the wo quantity. So I added the action set field value, during entry, then on the formula, put the internal ID of the standard field showing WO qty. And that is what I source for the saved search. Only problem is that it is prospective approach so your data before will not have data but you can try to edit save the transaction to update the field. Hope it helps. I am also still looking for better solutions, so far that is what I have done.

Best regards,

Emil