https://netsuiteprofessionals.com logo
Join SlackCommunities
Powered by
I pulled in a workflow that was created in the UI ...
# sdf
j
I pulled in a workflow that was created in the UI and when I goto validate it, there is the following error:
Copy code
An error occurred during custom object validation. (customworkflow_inv_sendtobillingacct)
Details: The sender field for the workflowaction584 (sendemailaction) subrecord must not be ACCOUNT_SPECIFIC_VALUE.
File: ~/Objects/customworkflow_inv_sendtobillingacct.xml
But the workflow is built fine and works.
s
This means the workflow refers to one or more values (usually internal ids) that may be different on a target system, causing unexpected problems if you deployed with those hardcoded ids.
perhaps look at the XML file and see where [ACCOUNT_SPECIFIC_VALUE] placeholders exist and either give them values or leave them blank with intent to edit the setting on/after deployment
j
thanks @stalbert, this is the XML part that references it
Copy code
<workflowactions triggertype="AFTERSUBMIT">
  <sendemailaction scriptid="workflowaction584">
    <attachmentfield></attachmentfield>
    <attachmentfile></attachmentfile>
    <attachmentjoinfield></attachmentjoinfield>
    <attachmenttype>SPECIFIC</attachmenttype>
    <body>Testing invoice send.</body>
    <conditionsavedsearch></conditionsavedsearch>
    <contexttypes>ACTION|BANKCONNECTIVITY|BANKSTATEMENTPARSER|BUNDLEINSTALLATION|CLIENT|CSVIMPORT|CUSTOMGLLINES|CUSTOMMASSUPDATE|DEBUGGER|EMAILCAPTURE|FICONNECTIVITY|MAPREDUCE|OFFLINECLIENT|OTHER|PAYMENTPOSTBACK|PAYMENTGATEWAY|PLATFORMEXTENSION|PORTLET|PROMOTIONS|CONSOLRATEADJUSTOR|RESTWEBSERVICES|RESTLET|ADVANCEDREVREC|SCHEDULED|SDFINSTALLATION|SHIPPINGPARTNERS|WEBSERVICES|SUITELET|TAXCALCULATION|USEREVENT|USERINTERFACE|WORKFLOW</contexttypes>
    <eventtypes></eventtypes>
    <includeformat>PDF</includeformat>
    <includerecordlink>F</includerecordlink>
    <includetransaction>T</includetransaction>
    <isinactive>F</isinactive>
    <recipientbccemail></recipientbccemail>
    <recipientccemail></recipientccemail>
    <recipientemail></recipientemail>
    <recipientfield>[scriptid=custrecord_billacc_contacts]</recipientfield>
    <recipientjoinfield>STDBODYBILLINGACCOUNT</recipientjoinfield>
    <recipienttype>FIELD</recipienttype>
    <scheduledelay></scheduledelay>
    <schedulemode>DELAY</schedulemode>
    <schedulerecurrence></schedulerecurrence>
    <scheduletimeofday></scheduletimeofday>
    <scheduletimeunit></scheduletimeunit>
    <sender>[ACCOUNT_SPECIFIC_VALUE]</sender>
    <senderfield></senderfield>
    <senderjoinfield></senderjoinfield>
    <sendertype>SPECIFIC</sendertype>
    <subject>Test Invoice Send</subject>
    <template></template>
    <usetemplate>F</usetemplate>
    <initcondition>
      <formula></formula>
      <type>VISUAL_BUILDER</type>
    </initcondition>
  </sendemailaction>
</workflowactions>
Im just surprised it would pull it in with a placeholder instead of the value that is currently set in the UI
s
I believe they do that for safety - basically I don't think they (NS SDF) wants to risk someone just pulling down something with account specific values then pushing it to another account where those values differ
j
ah makes sense, thanks
s
in your case, say you had employee 4 that is Joe Schmoe for the sender
if employee id 4 was someone else on your target system, the email would come from that other person if you deployed it as is- oops!
👍 1
j
yeah totally
e
You can see more in 
Help:Account-Specific Values
Most importantly, you can decide on a per-project basis whether you receive this message as an Error or Warning
2 Views
Open in Slack
PreviousNext
Powered by