Dext3r Bronze Trophy

Hiya, I believe this should work, though I wasn't sure in my instance what fields I could use to test the minuets on. I see you're converting the dates into MM/DD/YYYY HH24:MI:SS, so you may just need a little tweaking to it, but the math of my process and how I end up with a concatenated string of hours and minuets should…

I personally would build a Client script for sure, in a lineInit or validateLine function. Or a User Event script beforeSubmit. With lineInit, this would be when you start to add a new line, you could either have it fill in a default value or get that value from somewhere else on the form like a main line expected receipt…

I think you were right to log a support ticket, it sounds like something they're making changes on the backend. Especially with the behaviour changing despite you not making any changes. I remember once they made changes that completely broke Customer Segments on our SuiteCommerce Webstore until they reverted the change…

C 😁

What an odd forum for a bot to spam and try to gain interaction.

Ahh, how frustrating. Sorry Elina! There does seem to be some kind of piece to this puzzle that we're missing.

If it's a custom checkbox, this should be all you need; Set the access permissions per role you want it to effect. Here I add the Lapwing - A/P Analyst role and make it so they only have View access to my For Courier checkbox. For your case, if it's just 1 role you want to give edit permission then perhaps set the default…

I believe this is defined by the criteria. If you set a criterion with a specific selection and you are allowed to also add that field as a filter (some fields don't allow you to place them both as a criterion and as a filter) then the search should load with the filters set to those of the criteria. I quite frequently do…

The Default Text Field Filter needs to be 'Has Keywords', not 'Contains'. At least, that' what worked for me.

I dunno if this is possible with the default fields. I think you would need to build your own field that references and links to the contact list so you have more control over the data type.

Ok, it looks like it might also depend on if the the field is custom or not. Could be something else but here's what I achieved: I was originally testing this on Driver which is a custom Text field to no avail. I only managed to get it to work on Document Number/ID which I'm pretty sure is also a Text field but not custom.…

Mm.. yea I can't figure it out either. Apparently a prerequisite is that you need to set the filter to be a 'Contains' type, but I tested this and still couldn't get it to work.

My first instinct would be to try , or OR or AND as separators instead of |. This Stack Overflow thread also suggests it should be a comma. I otherwise do not have a definite answer for you. What SuiteAnswer were you looking at?

I dunno, from the way the checkbox setting reads it does seem to just be one option or the other. If you submit the return with -Empty- does that constitute as a No? But yea, certainly looks like room for improvement for this on NetSuite's side. It shouldn't be a list value, it should be a checkbox. And the setting should…

Thanks Angela, I'll give it some further thought. Glad to know there isn't anything glaringly obvious about my workflows being incorrect in some way.

Hey Angela, I'm not sure your approach suits my use case, or otherwise I'm not sure I understand your idea. To clarify, what I'm looking for are changes to the customer records item pricing. For when prices here are removed, which ones, hopefully why and by who.

Thank you both. Yea, if the system notes of a customer record already don't show item price changes, then would a System Note Search be able to yield different results? I'm already stuck in that Customer doesn't appear to be an available Record Type criterion in a System Note Search

Thanks both, just came back from a long weekend. I'm going to attempt scripting and let you know if I have any success. The Preferences of the User Role are good but lack a lot of the options, even Language doesn't appear to be an available option.

Changing the users Language settings from English (International) to English (U.K) has solved the issue. To apply this to all users without having them change their language settings, I have to reset the labels of my fields for one language, then change my language settings and do it again. So irritating...

Oops, I feel like I've asked this before. 'Ship Via' is the correct field. Perhaps I changed the label from 'Ship Via' to 'Shipping Method' at some point.

It's been a while since I used a One World account, but I hope this helps you. From my understanding, an intercompany transaction would have the Subsidiary as Subsidiary A and the customer would be a customer record representing Subsidiary B, is that right? In which case, you could use a numerical formula criterion like…

B 😊

Hiya, I'm not familiar with this field. Is it simply a checkbox? I'd start by including intercompany as one of your results and letting us know what results that returns. Chances are that since you haven't set Main Line to False as a criterion that intercompany is appearing on lines and not being handled properly. We could…

Thanks Richard, that helps clarify my understanding.

Thanks Jervin. Just gotta be extra careful then. 😅

Solved! There is an undocumented option you can use for submitFields() called disableTriggers record.submitFields({ type: so.type, id: so.id, values, options: { enableSourcing: false, ignoreMandatoryFields: true, disableTriggers: true } });

Hi Jervin, this is for future use cases. Is there a guide somewhere on how to use nlapiYieldScript?

Hiya, I believe you can do this by setting a criterion of 'Applied to Transaction' is 'Empty' And of course it also needs to be a Transaction type search with a Type criterion of is Journal.

This SuiteAnswer lead me to the answer. Creating Inventory Adjustments via SuiteScript Returns Unexpected Error One possible cause for this is because there are customizations that is trying to set the main body Location field on the Inventory Adjustment. The body location field on the Inventory Adjustment record…

Never mind, she just had the field group minimized. 😂 Since it was the last field group in the subtab, and the fields below it hadn't been assigned to a field group, it made it look like the fields had disappeared, not that the field group was minimized.