Matrim Bronze Medal

@brocha Delete this <hr /> tag on row 335 of your original template source code:

@Angelica Mae Segador-Oracle Thank you for those links, that was quite informative. Basically it confirms what @kees.netsuiteadmin and I have been experiencing, i.e. it is standard behaviour that table rows cannot be printed across multiple pages. So the workaround is to split up the contents into multiple rows instead.

@Angelica Mae Segador-Oracle I don't think this has anything to do with @kees.netsuiteadmin's template in particular. The same happens with any default template when you get very long cell contents. I'd also be interested in a solution for this. I've tried putting various CSS style tags like page-break-inside: auto or even…

@brocha Remove the part marked yellow above and put the border in the <tr> tag under the </thead> tag instead. Where you've put it is only 1 cell of the table header, and the error is because there are 2 style attributes within the same <th> tag. <tr style="border: 1px solid #dddddd;"> However, this will put a border…

Add Criteria → Standard → Transaction : Type = Invoice Change Summary Type of Results → Transaction : Date to Maximum Change Summary Type of all other fields in Results to Group Please note that this will only show items for which there exists at least one invoice, items without existing invoice transactions will be…

In the meantime, I've been able to solve the problem myself without making the change to SS2.1. So I'm still not sure as to the original question, but I guess I don't need the answer anymore. I've extended the script logic to dynamically create a search filter that's added to the existing transaction search filters, based…

@Richard James Uri-Oracle: Thanks for the reply and links. I've already tried some of the tips in the linked article, but it's not enough. It's quite a complex search (17 columns out of which 11 are formula fields) and I can't trim it down further for the functionality I need. Otherwise I'd need to run multiple searches…

@Mitzi B. sounds like you need to select summary type = group for the name field, otherwise it should be fine. In your post you have a typo on the closing } bracket, but since you're getting a list of roles I assume you have the syntax correct in your actual search. Thanks for making me aware of the LISTAGG function, that…

It should work if you add the width as an html attribute instead of css styling. Like this: <table cellpadding="5" width="100%" style="margin-top:2px;">

Interested in this, too, we have the same requirement. At the moment we are working only with memo fields and editing the blanket order contents each time a release order is entered, i.e. make one line for the remaining quantity (open / commit stock) and one line for the released quantity (closed / do not commit stock) to…

Edit: For custom fields @Tigran Shahnazaryan has posted the better method, my reply below assumed a standard field. To do what you are asking for dynamically (same link for all users but different columns displayed depending on user/role) is only possible by scripting, i.e. you would have to write a Suitelet that takes…

Hi @Preethi Kondur, it sounds like you are using a custom field to contain the work order number at the line level. You need to find out the id of that custom transaction line field, e.g. custcol1 Then you can add it somewhere in the #list section as ${item.custcol1} If you don't know where to find the field id, an easy…

@Paul L. Walker: Our packing slips (printed from Item Fulfillment) show both the parent item and the components of kits. So maybe it is an issue with your settings. My below reply is only for kits, because we don't use Item Groups. We do use Assemblies, but for Item Fulfillments or Sales Orders they act just like normal…

Hi @Kristoffer Viray-Oracle, thank you for the hint, I've figured out a workaround using a Workflow / Sublist Action Group on Before Record Load: [Condition] Created From Is Not Empty [Set Field Value] Line : fieldname=Line : Item : fieldname We only use this field for sales orders and there are no other transaction types…

You could make a new custom record type with fields List/Record (Saved Search) and Text Area to hold the necessary information. Really convoluted method, though, it would be very annoying having to create/delete those additional custom records along with saved searches every time.

@Vernita: The place of the </#if> is wrong, so the whole #if block is currently redundant. But also I disagree with the use of ?has_content, because this will evaluate as true if a checkbox has been marked as unchecked ('F') instead of being truly empty, i.e. it can give you a false positive. When you create a new field…

Checkboxes in Suitescript take values of 'T' (=Yes) and 'F' (=No), so you will need but in Freemarker it seems they are parsed to true and false. Please use: <#if transaction.item.custitem_discontinued == true> For comparisons you should use double equals ==

I guess best practice would be to make two check boxes as custom body fields on your transaction ("Contains back ordered items", "Contains discontinued items") and have them filled by a script or workflow depending on the contents of the transaction when it is saved. That is because in Freemarker you can only build up the…

Yeah, the only items that are not part of a subtotal are those at the end of the order after the last subtotal. You cannot have items inbetween two subtotals that are not part of either. Quick SS1.0 draft below. Not tested, you might need to exclude some other "special" item types if you are using them. Change…

This would be quite straightforward to create as a user event script (before submit). Loop backwards through the list of items; when you find a subtotal item keep looping backwards from there and set your "Is subtotalled" checkbox to 'T' for all non-subtotal items.

From the screenshots it looks like you're using the Inventory Status feature. Maybe you can resolve the issue by assigning an Inventory Status of "Good" to those 2000 liters to make them available by using the Transactions > Inventory > Inventory Status Change page as explained here:…

@Katerina Winklerova-Oracle: Actually there's a field for that called "Main Line Name" that you can select in the search result columns. This will display the vendor name on all lines even when filtered to main line = false.

You could make that work by using Custom Records to represent each row / overtime entry and making the employee a parent field of that custom record. Check out SuiteAnswers 38231 for an example. Just change customer to employee and add additional fields as required instead of "Custom Information" in the example.

I assume you're trying to use the ?number built-in? You forgot to include a screenshot. You can find some of the reasons why you might get an error in the documentation: https://freemarker.apache.org/docs/ref_builtins_string.html#ref_builtin_number

Terms are not on the Billing tab but on Main, in the Primary Information section.

I've also contacted support about this in the past. Would be so much better if it would at least default to the transaction number (when there is one) instead of the strange thing we have now (uses some hidden field called dbstrantype according to the XML view), i.e. COALESCE({tranid}, {dbstrantype}||'_'||{internalid})

I think the easiest workaround through scripting would be to set the rate field to amount / quantity. Or better yet to add that into the customization you are using.

Adding the permission is not enough to show it on your customers' dashboard. You have to go to Customization - Centers and Tabs - Center Links: Add a descriptive label (e.g. "Your Equipment") and copy the URL of the page you want your customers to see; this can be either the default list for your Custom Record or a Saved…

Very useful feature, I am using this regularly. Your note is definitely important and this part is a bit frustrating, because it involves a lot of trial and error. There are some fields which you can only find in the XML view and which aren't documented anywhere. But that doesn't always mean that you cannot use them. For…

We had this requirement, too. I solved it by using a Custom Record with various additional fields: customer, item, MOQ, reason (text field to record comments why the customer has a special price), valid from date, valid until date, unit price (fixed price), discount rate (percentage from list price). Plus a few fields…