My Stuff
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Comments
-
We to have run into this issue and have tried several things. 1. We tried the custom record approach where you have to do multiple imports (3) to get in the history of the contact's campaigns. This proved very cumbersome and the attributes of the campaigns were getting unmanegeable. For example, a webinar woudl have…
-
That worked, thank you.
-
That did it. Thank you very much.
-
I am having the same issue with the aging history reports. The numbers do not match up with the pipeline.
-
I have created a way to do this with JavaScript code and custom fields. Fairly easy to do. It is calculating the days in status off the lead accepted date and days in pipe off created dates. If you want the script let me know and I will post it.
-
Thanks so much that did it. Here is the code I used: else if (nlapiGetFieldValue('entitystatus') == '13' && nlapiGetLineItemCount('competitors') =='') { alert("You must enter at least one competitor before saving a closed opportuntiy. If you do not know chose Unknown"); return false; } Thanks again.
-
I have used the SF version via the App Exchange and it does exactly what you want it to do. Would be a very useful data cleaning integration.
-
Nice, that did it. The way I searched for it is on the label. If you look for the label name it shows you the internal id. My example was this. ftabs['custrecord_targetedaccountslabel']='custom28'; Thanks again.
-
I went back in today to see if it was fixed. And it does not appear so. Now I am trying this in my sandbox account does that make a difference? I get an error now: Error An unexpected error has occurred. Please click here to notify support and provide your contact information.
-
What if I have already created a hundred or so fields on several different custom records. Do I really have to go in and make new fields? That seems crazy. Or do I only need to change the one field that is being called in the script, in this case the name of the sales rep. I am confused on this a bit. Do I change only the…
-
Thanks I will give it a try.
-
One more question. Can we extend this to include another scenario where the parent is the Custom record to the opportunity? I have territory plans where I want to pull in the top 5-10 opportunities to the plan. The parent again is the custom record. I am trying to link the opportunities to the territory plan via the sales…
-
Ok and thanks for all your help. Glad to know its not me.:rolleyes:
-
I put in this but it threw an unexpected error. I am not sure if I substituted the right code. Sorry not great at the coding part. function beforeLoad(type,form) { if (type == 'view') { var rec = nlapiGetNewRecord(); var emp = rec.getFieldValue('custrecordsalesrep'); //alert(emp); var filters = new Array(); filters[0] =…
-
I made the changes to but still get the same error. I am overwriting the script every time when I make changes is there something else there I need to do? function beforeLoad(type,form) { if (type == 'view') { var rec = nlapiGetNewRecord(); var emp = rec.getFieldValue('custrecordsalesrep'); //alert(emp); var filters = new…
-
Here is what I am using now, the alert throws a value of 10632 so it is not null: function beforeLoad(type,form) { if (type == 'view') { var rec = nlapiGetNewRecord(); var emp = rec.getFieldValue('custrecordsalesrep'); alert(emp); var filters = new Array(); filters[0] = new nlobjSearchFilter('salesrep',null,'anyof',emp,…
-
I am getting the following error: An nlobjSearchFilter contains an invalid operator, or is not in proper syntax: salesrep. Here is my code: function beforeLoad(type,form) { if (type == 'view') { var rec = nlapiGetNewRecord(); var emp = rec.getFieldValue('custrecordsalesrep'); var filters = new Array(); filters[0] = new…
-
Ok it is fixed now. The issue was a capital C for Custom. Stupid syntax. Here is the working code for anyone who wants it. function beforeLoad(type,form) { if (type == 'view') { var rec = nlapiGetNewRecord(); var emp = rec.getFieldValue('custrecordsalesrep'); //alert(emp); var filters = new Array(); filters[0] = new…
-
Evan, Did you use the following code in the Page Init Function calling the beforeLoad function? Trying to make sure we did the same thing. function beforeLoad(type,form) { if (type == 'view') { var rec = nlapiGetNewRecord(); var emp = rec.getFieldValue('custrecordsalesrep'); //alert(emp); var filters = new Array();…
-
Ok that seemed to fix one issue. But now I am getting this: ReferenceError: "fld" is not defined. (beforeLoad#13) How do I need to define fld is that that name of the field reference. function beforeLoad(type,form) { if (type == 'view') { var rec = nlapiGetNewRecord(); var emp = rec.getFieldValue('custrecordsalesrep');…
-
Yes I have tried many variation and keep getting the same error. At a loss at what to try now.
-
Ok I went the route of the opportunity search. I now have data showing up but how do I limit it to the only show the contacts on the "current" opportuntiy?
-
Is there now way then to pull in information from the parent to the child in an array format? Such as contacts, competitors, etc. I would like a list of these on the custom record.
-
Yes it works just fine. But when combined it fails. The script fails when I change the tab name away from custom. If I put another name 'targeted' for instance it fails. That is probably the issue. I thought you could dictate which tab the list appears on. This fails only becuase I changed it to targeted and not custom. I…
-
My follow up question to this is can you do more than one list in the beforeLoad. I get an unexpected error with this code and I am not sure if it is syntax or just not possible. function beforeLoad(type,form) { nlapiLogExecution('DEBUG','Plateau','This fires'); if (type == 'view') { var rec = nlapiGetNewRecord(); var emp…
-
I opened a case #638293.
-
Thanks for your help and work on this.
-
Ok tried renaming and get the same error: Notice (SuiteScript) You have entered an invalid form element name. It must be prefixed with "custpage", unique, and cannot contain any non-alphanumeric characters in order to be added to the form or sublist. There is no line number. Here is the code I am using now. function…
-
What I am trying to do is little different. I have a custom record that is attached to an opportunity. It is an opportunity plan. What I want to do is pull on to this plan (custom record) a list of the contacts on the opportunity. For example, part of the opportunity is an org chart. I want to be able to understand the…
-
This is a custom record and the subtab Targeted does have a field on it. However I still get the unexpected error.