Paul L. Walker Red Ribbon

It looks like that was it. If we continue to have the problem I'll check back in. Thanks!

I did open a case with NS support and found out from Tony that global search results are limited by design for performance reasons. He didn't say exactly what the limit was, but I think that qualifies as an answer. A related issue is why we can't use sorting to overcome this limitation. In our case this would mean sorting…

I'll take that advice. Sorry I couldn't mark an answer, but I really appreciate your help investigating this.

Well, after waiting overnight I'm seeing the same item global search results, for "shelf" as well as "freezer" and "fryer". Right around 260 results. Before I remove all of our long descriptions I noted that there are some items returned in the Item page search for "shelf" that don't have anything in our custom long…

This doesn't seem to explain why the global search results always include items that are alphabetically first. But I have unchecked that box, I will check back tomorrow to see if there is a change, and I will report back. Thanks again Tigran.

That's sounds like a distinct possibility, as we import our long descriptions and they frequently contain special characters. The custom text box that holds these descriptions is marked for global search. I've tried un-checking that box, but the global search result is the same. Is it possible that once they are indexed…

Thank you , and since our crisis seems to be on hold for the moment... Using Display Name as the filter instead of Name yields 1667 results for "shelf". I'm not sure which discrepancy you were referring to, but I don't think this explains the difference between the global item search results and the item search results.…

I apologize, but I will have to put this on pause as I have a different NS issue that is very pressing. I will return to it asap, and Tigran I really appreciate your help and persistence!

I entered "ite: %shelf+" in our global search and got 267 results. I had switched the search back to MB List w/ Qtys, since this is a live system and I don't want to disrupt our users too much. That's interesting about ADVA-AG-MT-300. It appears that under a "Name" search NS includes the Store Display Name field along with…

Incidentally, I tried switching the global search to the new Custom Item All View and I got 271 search results on "shelf". Nowhere close to 1777 😕. Including inactive items may account for the difference between that result and using MB List w/ Qtys.

I did that and used a "=match()" formula in excel to see which of the items in the Item export matched the items in the global search export. I'm attaching the two files, though I removed the formula from the first, leaving just the result values, so the reference wouldn't break it. The result isn't as clean as I…

OK, following your instructions led to the creation of a search called "Custom Item All View" and the only changes I made were to add Name as an Available Filter and to change the default text search to Contains (to mirror my other search). Is it important to test with the default, Starts With? My results: "freezer" - 388…

Did you want me to use this for the global search or just on the Item page?

I don't think that is the issue, that my results on the Item page are being padded by duplicates. My testing: I changed that filter to Name (Internal) and now I'm getting these results: "freezer" - 9; "fryer" - 0; "shelf" - 14; This is apparently because Name (Internal) is what we would call the item code (or item number,…

By "global search" I mean the search box always present at the top of the page in NS: And to clarify my observation about the number of search results: If I type in "item: freezer" or "item: fryer" or "item: shelf" into the global search I will get around 259-265 results. But if I go to the Item page (below) and type…

I also tried a few very general global item searches just now and noticed the number of results is always very similar, ranging from 259 to 265. The number of results for these searches varies widely (388, 510, 1777) for identical searches on the Item page. Maybe this is a clue?

Hi Tigran, I tried unchecking that Preferred Search Results box and the global item search reverted to a search called "Preferred Item Search Results" (viewable by the same method as above, clicking Customize and then More Options) with different columns, but the global item search was still cut off somewhere in the Hs,…

Sure thing. I'm doing an item search in the global search bar, and then clicking the Customize button - That takes me to this screen. "MB Item List w/ Qtys" is a saved search I created. I usually click on More Options to open the saved search page - And on that page I believe this is option that designates this search as…

Thanks for your help. I've submitted the enhancement to SuiteIdeas to change this behavior. Seems like a simple, common-sense fix, so hopefully they'll make the change.

I still don't understand why a vendor prepayment would be sent to the drop ship address for a purchase order by default, or really anytime. Should I create an enhancement request to fix this, or is there a common scenario I'm overlooking where this behavior makes sense? It was helpful to know that the vendor's addresses…

Hi @Matrim, No, the parent items do not appear at all on our Item Fulfillment page, only the component items do, but I'm very interested to see that yours do. What makes the difference? Is there a setting that controls that?

I had this problem on a report, and what worked was going to the Filters tab and first making some selection for filter I wanted to be "all", then saving, then returning to the Filters tab and that filter, deleting the text in the box (with the delete key on my keyboard; not using the selection screen), then saving. The…

Hi @Angelica Mae Segador-Oracle, Thank you for your response. Two questions: Isn't there a difference between Assembly and Kit items? We are dealing with kits only. Also, this doesn't seem directly related to my issue because it is the parent of the component items (that's what I meant by the Kit/Group item) that isn't…

First, thanks to @Matrim for this very helpful post. I couldn't find "kitlevel" (maybe something has changed from 2021 to 2023?) but I did find a tag called "ingroup" (by using @Matrim's &xml=T suggestion and looking at the sales order from which my fulfillment was made) which I could use to indent component items by…

Sure, no problem. For an item on a sales order, change the Cost Estimate Type to Custom and then edit the Est. Ext. Cost field. Note that the PO Rate still reflects the Purchase Price (internal field ID: "cost") from the item record. It can be edited but doesn't change automatically. Sales order: Item record: After saving…

Idea submitted. Thanks @Michelle Jabanes-Oracle

I've got my issue figured out. The trick was to open a transaction (an invoice in my case) with the custom form in question and see if the custom field was visible. It should have been, according to the form customization screen, but it was not. (Sometimes these custom forms don't behave as expected...) So I used the "Move…

I'm having a similar problem, and maybe I can both help and get some help here. I created a custom field and applied it to only one of our invoice forms. When I went to import to that field, I forgot to check the Advanced Options where I needed to select the correct Custom Form so that I could see the field on the mapping…

We do have team selling set up, but we don't have the module that includes commissions ("Incentive Compensation"?). Maybe that is the problem here. Or we need a custom scripting solution like you suggested. If we could export a SuiteAnalytics workbook to an Excel or PDF, or if there were a join from a transaction saved…

#2: Our commission rate field is a custom field on the employee record. Should there be a commission field on the Sales Team sublist? We don't have the Netsuite commission module. Here is what that sublist looks like (with Team Selling turned on) on an invoice: I checked the invoice custom form and I didn't see any way to…