My Stuff
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Comments
-
You can use set the date field to null using workflow. Initiate only on create and trigger before record load.
-
If the fields are on transaction header, you can also use workflow to copy the original start date value to start date field.
-
Larry, For single JE approval, you can build a workflow to prevent current user from approving by disabling approve button/checkbox. For mass JE approval, you can workaround the issue like this : 1. Remove Approve Journal permission from all users. 2. Create a suitelet (execute as admin) that searches for all JEs pending…
-
Multiple script deployments on same record are executed in the order specified in the UI. Go to your record from scripted records view and move the scripts up or down as required. Thanks, Asif
-
If you're using custom PO approval workflow, you can add a 'View Record' link on the emails.
-
On Approval, are you transitioning to another state and setting status = Approved. Also, mark this state as 'Do Not Exit Workflow' so it won't restart again and again.
-
You can also use workflow to remove 'Email' button if the status is not approved (or later).
-
You can implement the following to fulfill the requirements : 1. Create a saved search for bills that are not approved. Make this saved search available for reminders. For each user that needs to see unapproved bills as reminders, you can setup the reminder portlet to include this custom saved search. 2. As for auto…
-
Alan, You cannot pass search results into workflow to be used in set field value action. You do have two other options : 1. Use condition on set field value action. You can use join fields to build your condition. 2. Use a workflow action script to call the saved search and pass back the results to the workflow to be used…
-
This is from help documentation. Hope it helps. Workflow Action Scripts Workflow action scripts allow you to create custom Workflow Actions that are defined on a record in a workflow. Workflow action scripts are useful for performing actions on sublists, as sublist fields are not currently available through the Workflow…
-
Do you have store value = T for all the custom fields ?
-
Alan, There is a very simple example of workflow action script given in help documentation at - SuiteFlow (Workflow) : Customizing Your Workflow : Using Workflow Action Scripts. Hope that helps. Asif
-
Hi Jeff, You can create a workflow on Vendor Payment record. Initiate on create, after record submit. In the state use 'Go To Record' action and select Record Type = Check. Enter any default values you may want. The workflow will create Check record for you every time a Vendor Payment record is selected. Hope this helps.
-
Jeff, The workflow is running off of Vendor Payment record and is initiated only on create of vendor payment. So it will create a check when VP is created (you'll need to set appropriate conditions to check on VP - like "Wired" word in Check # field). You can default check record values in Go To Record action itself, or…
-
Is this custom field a workflow field or state field ? Also is it of type = list/record and list = transaction ? Try to store cash/cc sale id in a custom field on the SO and then use this field to go to cash/cc sale record.
-
Where is the ID for Cash/CC Sale record stored on Sales Order ? You need to use that field in the ID.
-
Matt, What is your transition condition ? Asif
-
Do you get this error when you set the value manually in UI ?
-
Yes, initiate the workflow on create of Item Fulfillment record. Use Create Record action after record submit and if order condition is met to create a new task of type = call.
-
For some reason, button Id drop down in remove button action is empty for custom records. I'd suggest you to log a support case for this.
-
If you're trying to create a workflow, then log in as admin and go to Setup -> Customization -> Workflows -> New.
-
You can use send email action on condition Old Record field value <> field value, triggered after record submit. You'll have to do this for all the fields that you want to 'monitor'. Alternatively, you can send email via scheduled saved search if order is updated in the past 24 hours.
-
You can get Id of saved search from Saved Searches list view. It'll start with customsearch. Is this what you were looking for ?
-
Remove the first 'After Record Submit' trigger on workflow. Let the workflow initiate on ALL events and actions be triggered after record submit.
-
I am assuming that you are using a scheduled script to update records. In this case, user will not be admin, it will be system. Can you execute lock record action only when context is UI ?
-
Can you use a WF action script to return last email received date by customer and if not today then send email.
-
What's the trigger on Go To Record action. It should be 'Entry' in your case.
-
Is the record type same for both the source and target fields - date or date/time ?
-
Try TO_CHAR({today}, ‘mm/dd/yyyy’) = 05/31/2011 to check for today = 5/31/2011 condition.
-
I am not aware of number of workflows limit on a record. There is however, a governance limit as stated below : Workflow Governance The total number of units available across all workflows for a record type (for a given triggered event) is 10,000 units. Within one state, all of the actions combined cannot not exceed 1000…