My Stuff
Comments
-
Hmm, good to know. Thanks. We did put a case in but I'll have the other dev check on the work around.
-
Also, this was our sandbox and I just reproduced the behavior in live.
-
Yes. Is that the problem?
-
This is on a new form.
-
Is there any reason you couldn't just check for the existence of the jQuery object before downloading your script? It is included in the UI now.
-
I was just showing how to create a cookie, you would have to tailor it for you own needs.
-
Here is a function I use to keep a pop up form happening unless two hours have passed. // Create a cookie to show the allerts every 2 hours function createCookie(cookieid){ // set a new cookie expiry = new Date(); expiry.setTime(expiry.getTime()+ (2*60*60*1000)); // Two hours // Date()'s toGMTSting() method will format the…
-
Actually, the version included with NS is Ext-3.3.1. I don't think there's a big difference between 3.3.1 and 3.4, indeed the 3.3 samples site takes you to the docs for 3.4, but just in case....
-
I will second making them inactive. Much safer that way.
-
Evan, that ended up not being what the finance and sales guys wanted. I added a button with the following code: //Called on an opportunity to get the parent companies activities. function parentActivityHistory() { //Show activity button on the Edit mode of the Opportunity form //Get the OpportunityId and put it in a…
-
Thanks. I voted, but there are only 15 votes so far. I am not holding my breath.
-
Same here.. too often i have a 2nd page generated on a transaction but for a single line - has to be a better way than this! Seamusmon Along these same lines (multiple page transactions) is there a way to have the signature line that I have in the PDF layout to only go to the last page? I am looking still, but so far all I…
-
I am trying to do the same thing with a couple fields on our form. Did you ever come up with a solution? The only thing I can think of is a different field (drop down) for each of the three roles. I would prefer to make two drop downs, with one dependant on the other.
-
Is this still not possible? I have been merging a form using a PDF layout in script for a while and I am just now being told that the custom field in the PDF layout is not extending to a second page. IS there a work around other than going back to nlapiXMLToPDF? :h_a_w:
-
I should have mention in my previous post that this is totally possible with the nlapiXMLToPDF API. It's a PITA, but it's possible.
-
I've seen this, too for custom records. Ours start jumping by 100 and it's on several records we use. It's an odd artifact and we have never gotten to the bottom of it either. Nor has support when we brought this up. It would be nice to know the answer.
-
Weird. I hadn't realized it had been fixed so I never save the default text.
-
The in app template editor has always been broken for me. Even on default layouts. I use a text editor (currently Google Web Designer), copy all the text from the layout, fix the parts where the editor breaks it (usually a mis-parsed if or loop), make my edits and paste my code into the space and save.
-
Just for clarity. This problem is not with Freemarker templating or the BFO engines this is an artifact of the in app editor.
-
Ideally, I would like to just create these in the IDE and bypass the editor altogether. That way we could/should have objects available for code completion.
-
Oh the layout works just fine. I just can't edit it again in the editor. This is why I use an external one.
-
That is the main issue I had building out custom PDF's before this version came about. You have to make the source of these be strict XHTML, which requires a couple things. Quotes around attributes and all tags closed, for instance. Another thing it requires is special characters (&, ;, \n, ,etc.) need to be escaped. When…
-
So, the default ones will save for me now, so apparently that was fixed. Bear in mind that I am still on 2013.2. With my custom layout I get the following: The template cannot be saved due to the following errors: Encountered "<" at line 117, column 17 in template.. Was expecting one of:. <STRING_LITERAL> .... <RAW_STRING>…
-
The only problems I ever had were with spaces, new lines and ampersands, so it wasn't a big deal to parse those out. I ended up making a prototype for spaces so that I could have description items indent a number of spaces as the generator didn't respect them. Also, I didn't realize that function existed until I was done…
-
but I am pretty sure the new SSP functionality is what they are calling the new "Ignite" interfaces. My understanding is that the API's they've provided with SSP are based on the Ignite API's. That was my understanding as well from the breakout (SuiteCloud track) where Elham was talking about SSP at SuiteWorld. At this…
-
I have the same(ish) script set as a library and use it on my scheduled scripts but I just this week noticed that I don't have handleScriptRecovery() defined. What do you have for that?
-
Or, do both. I have several scheduled scripts that key off searches that looked for a check box and utilize a library script I put together that will yield when appropriate. i don't know how many records you have or will ever have but if you want to do something like this on a large number of records every month/day/hour,…
-
No one? >10 chars
-
No, I have that as a hidden column field check box.
-
Trying to parse a SOAP response will be tedious. Well, I find XML tedious, regardless but that might just be me. If you look in the help there is an XML API and some examples in SuiteAnswers: https://netsuite.custhelp.com/app/an...2/kw/xml%20api