gokuakuatsushishoukai Bronze Medal

@Kristoffer Viray-Oracle I appreciate your help. About Tax ID, I understood. But "Account" is not the one of invoice that you said, it's on Purchase Order form defaultly. (So I believe it has nothing to do with Account Receivable...). Please check the specification of the Purchase Order's "Account" field under the…

@Jack Daryl Espiel-Oracle I appreciate your help. Could you give me a sample code of what you taught me? The simple one is fine. I would superly appreciate it. Best Regards,

@Nicole Mendoza-Oracle I appreciate your help. I've not yet tried putting a client script on a suitelet. How can I do the implementation?

if you put a value on an ETA field other ETAs are also automatically changed. This is the image of what we need.

@Richard James Uri-Oracle No worries, understood. But then, how can I get the text value in this case? I guess there must be the way. @Nicole Mendoza-Oracle

@Richard James Uri-Oracle I met the following error. TypeError: context.request.getSublistField is not a function In your end did it work?

@Richard James Uri-Oracle I appreciate your reply. Then, Im the case the field is disabled, is it possible?

 context.request.getSublistField({ id: 'custpage_field', line: 0 }).getText(); I guess the above doesn't work,right? We need the current text at this point(Our Suitelet is editable), so I think... we have to get the text from context.request. How can we do that? @Richard James Uri-Oracle I appreciate you helping us.

@Joy Noreen Magoling-Oracle I appreciate you replying and sharing this case with @Richard James Uri-Oracle and @Nicole Mendoza-Oracle . I hope we got the solution soon. Best Regards,

Could I get the number of the request?

@Kristoffer Viray-Oracle @Katerina Winklerova-Oracle Hello, I'm sorry for bothering you guys but could you confirm my last message?

@Nicole Mendoza-Oracle We highly appreciate you helping us, it worked fine. Best Regards,

@Nicole Mendoza-Oracle

define(["N/record",'N/currentRecord'], function (record, currentRecord) { /** * @NApiVersion 2.X * @NScriptType ClientScript */ function pageInit(context) { } function airisReference(context) { const customFieldPrefix = "custbody"; const customRecordPrefix = "customrecord"; const airisMasterId = "_airis"; const…

@Nicole Mendoza-Oracle I appreciate your help. But I met the error "Syntax error: syntax error" when I rewrote "2.1" to "2.0" and tried saving it. But I can't understand which part is Syntax error in 2.0 script. Could you check it and tell me where I should fix it? Best Regards,

@Richard James Uri-Oracle I appreciate your sample code, it is super helpful. But I met the following error and can't save the script modification. Fail to evaluate script: {"type":"error.SuiteScriptModuleLoaderError","name":"SyntaxError","message":"SyntaxError: /SuiteScripts/tamura/auto_receipt.js:28:28 Expected ident but…

@Richard James Uri-Oracle I appreciate your reply. But If I remove the following part from our script, the transform successes all the time. newRecord.setSublistValue({ sublistId: "item", fieldId: "location", line: 1, value: locationId, }); So, I think the PO's approved and all requirements are also contained. That's why…

@Katerina Winklerova-Oracle I appreciate your reply, and I'm afraid that I've not yet found the cause because NS doesn't give it to us with the log. Just UNEXPECTED_ERROR doesn't make sense so I would like you guys to investigate what causes this error. Best Regards,

This script is the WF script. When POs are approved, it works.

@Nicole Mendoza-Oracle I appreciate your reply, but it was not what I wanted. But at first, there was a massive lack of information from my side, sorry. Our suitelet page searches transactions and display them as an editable table. And this is the worst point: we have more than 10 table types. So if you write it with the…

@Kristoffer Viray-Oracle I appreciate your reply, understood. Is it also impossible to apply a script to forms and to add the properties of page elements? And I also want to get the link to the enhancement page. Best Regards,

I think there is no place to configure it in the normal specification, so isn't there a trick to do that?

@Micah Timbol-Oracle I appreciate your reply. Hopefully, @Richard James Uri-Oracle and @Nicole Mendoza-Oracle will provide us with the solution. Best Regards,

@Richard James Uri-Oracle I have to explain to my customer why this limitation occurs, so I'm afraid I've not yet got enough information from you guys. Did you see the logs that I attached and confirm that it is wired? (search.Column return surely has "type, I think it is completely clear.)…

And if you can confirm this issue, could you raise the support case to vote for us? (Because at this point we've not yet started using our Production so this is still the SB issue. This problem has to be solved but some support stuff ignored and closed the SB issue before even though I raised the support ticket. So I would…

@Richard James Uri-Oracle I appreciate your reply, but I want to clarify, the column field name is available(because I can reach the value with Column.name), but the type is not possible because of a bug, is it correct? search.Column result surely has not only "name" and "label" but also "type", so I have no idea why it…

@Jack Daryl Espiel-Oracle I appreciate your reply. The reference that you sent resolved our concerns. (CLOBTEXT was the internal ID of "LONG TEXT" type, I should've referred to the Suite Asswers before asking. I ought to apologize for it.) Best Regards,

@Jack Daryl Espiel-Oracle I appreciate your confirmation. What we're thinking of is "Custom Fields that are created in Customization > Lists, Records, & Fields > [Field Type] > New?" Best Regards,

@Richard James Uri-Oracle I appreciate your confirmation. I understood. I would like to request you create this support case instead of us because this is our SB issue, not the production so they won't handle the case. (Last time, I raised the case about the SB issue but they closed it because they consider that the case…

@Richard James Uri-Oracle I appreciate your reply. Here is our currency list and the base currency is JPY, whose precision is 0. So still struggling the reason for this .00 behaviour.