I created workflow that will send an automatic email and create case record when user create order. The email sends and a case record is created but I have problem that some fields not transferred.
For example, I tried to pass the 'Order Requested Delivery Date' field to the new case 'Description' field. The case record created but the description field is empty.
I would check 3 things.
1) is the "Order Requested Delivery Date" populated on the source record (order)? Sometimes field names can get mixed up easily or you can be pulling the correct field name but from the wrong table
2) What does the audit history of the created record say? Was the field set on creation and then subsequently removed for one reason or anything?
3) Are specific fields on the target record not ever populating? Data type mismatches could be the culprit here.
Related
I have a tab that i would like to show ONLY on purchase orders and not other transaction types. That tab essentially has an associated custom record's fields on it.
First I made a custom TRANSACTION subtab called "PO Acknowledgement Tab".
Next I have a custom record that I would like to be related to purchase orders only. I made a custom record (call it PO Acknoledgement) that has a number of fields (one of which is a field that is a 'parent transaction' ("record is parent" setting on the field is checked) field that points to the transaction. and of this parent field on the bottom is select that new tab I created. The rest of the fields have no tab set.
This shows just as I would like but the issue is I see it on ANY transaction since the "parent" record field is a Transaction and I cant figure how to filter to only show this tab on PO screens. How would this need to be done to accomplish that?
First is a screen shot of the field inside the custom PO Ack record
And below is the full PO Acknowledgment Record
WS Was correct it seems. "In your custom field, in the Sourcing & Filtering, can you add a filter Filter Using = Type with Compare Type = equal to Value Is = Purchase Order and see if that restrict it to only the PO form? –
W.S"
I am writing some code to integrate with our installation of NetSuite. We use a service by CData to replicate the primary NetSuite tables down to our local SQL Server. My code will send an electronic invoice (outside of NetSuite) but I don't want to send it if it has already been emailed from within NetSuite using their built in feature.
The "Invoice" table contains all the main header info for invoices and there is an "Email" column in there. If that field has a value in it does that mean the invoice has been emailed? Or can someone fill in that field WITHOUT emailing the invoice? (I need to know if the invoice has in fact been sent)
The email column should be the email on the communication sub tab.
You can see if an invoice has been sent the "Message" sub tab in communication. If the record in there is a type = "email" then the message has been sent through Netsuite's internal functionality.
Does that help? Also, can I ask if you were successful with this? I am also looking to send emails using a CData connection.
I was looking for a status that would indicate if the invoice had been printed or not. Didn't find it. The solution could be to build a custom field on the transaction called 'Print status'. It would be a drop down list with 3 possible values: Pending, Printed Original and Printed copy. Set the field to 'Disabled' and its default value as 'Pending'.
We could go further and add a custom field called 'Date last printed' and even a 'Last printed by'.
Then we can build a workflow of action type 'Set field value', the condition of Field value = 'Pending' and an action to set the 'Print status' to 'Printed original' once the invoice is first printed.
A second action to set it to 'Printed copy' if someone reprints the invoice.
Using 'Set field value, we can also chane the transaction form to one that points to a pdf template with 'COPY' on it.
My issue is that the standard Action, Print of the invoice does not trigger any action on the workflow. So I guess we should look into building this via script.
Let me know if you find an easy workflow alternative.
Good luck.
I've created a custom Transaction Body Field named "Created From" of type List/Record - Transaction
That I want to be have like the native NetSuite Created From fields. I have added this custom field to the Customer Refund form and when entering (or editing) the refund if I give a value of "Sales Order #1234" it saves correctly and becomes a link to the sales order. But when I try to set it using code
customerRefund.setFieldValue("custbody_ifx_created_from", "Sales Order #" + salesOrderId);
id = nlapiSubmitRecord(customerRefund);
This error is generated
Error: INVALID_KEY_OR_REF
Invalid custbody_ifx_created_from reference key Sales Order #81388396.
How can I create a valid key or reference to another record?
The type of your custom field is list/record->transaction. You need to populate it with the internal id of a transaction record. That will allow you to submit the record. When viewed through the UI, it will display the 'Sales Order# XXX' text as expected.
customerRefund.setFieldValue("custbody_ifx_created_from", salesOrderInternalId);
id = nlapiSubmitRecord(customerRefund);
I have a requirement where i should display the details(values) of the custom record in the suitelet sublist.
Now i have to create a custom Record with two fields. One field would be bill payment and other field will have list of bills related to bill payment.
When i create a custom record what should be my field vaues's type?
Appreciate any help.
I would suggest to keep one field of type List/Record and Record option to "Transaction", and second field of type Multiple Select with record option to "Transaction".
Since, the fields can hold reference to any transactions I would recommend writing a user event script which would fire on create/edit and validate that the fields value are always correct.
We've created a pretty standard issue tracking system based off of SharePoint's template with just a few extra columns. On the list view (AllItems.aspx), the first column is called "Issue ID" and has a number. Our developers and QC use that number in discussions. However, that number doesn't seem to want to show up on the detail form (DispForm.aspx) nor in the alert email.
Can this field be included in at least one of these communication methods? If so, how?
Thank you.
We did something similar and used workflow via SharePoint Designer to copy the ID field into a field called "Issue Number". The workflow gets triggered automatically on Create / Edit (we included edit because the field can be modified by the user on the edit form and if that happens we want the number refreshed with the actual ID).
Before you create the workflow in SharePoint Designer, you need to add a column called "Issue Number" to the list you want to tweak.
List item
Open Sharepoint Designer
List item
Click File New -> Workflow
Give a name for the workflow
a. select the list from the dropdown
b. Uncheck Allow this workflow to be manually started and check automatically start on new and change then press Next
Give the step a name like "Assign Issue Number"
Create a Condition
If Compare a field -> If Issue Number not equals Current_Item:ID
Create an Action
Update List Item -> Set Issue Number to Current_Item:ID
Press Finished and test out by creating a new issue.
*The Issue Number will appear on the form and if you have emails setup to notify on assignment it will appear in the reassigned template.
*It will not appear in the created email confirmation because the workflow gets triggered after that email was executed.
I just added the issue ID using a total of 4 characters. Create a new column, set it to a Calculated column, in the formula type [ID]. Voila! The ID is now in your detail view.
The ID link returned the for me, however, the work around which sufficed for me was to enter 'Created' in the Calculated Column formula and ensure it is set at date and time. That then creates a unique idenity (unless you receive more than 1 list update per minute) than can be viewed in the email alert message