https://netsuiteprofessionals.com logo
Join Slack
Powered by
does anyone know what the limitations / issues are...
# administration
a
does anyone know what the limitations / issues are around putting in a large amount of addresses for customers? e.g. if i load a customer up w/ ~1,000 different addresses, what problems come up there?
k
Mainly it's a giant fucking pain in the ass to deal with
You can't find an address to update it on the customer.
cause the drop down is capped at 25
In theory there's performance issues as well - but NS seems to either have resolved them or I just can't find the article that tells you not to do it
That said - I did have a client a few years ago that I found an explicit indicator discouraging use over 100 addresses and indicating that there were issues with over 1000
but I can't find it anymore
You can mitigate the address updates with a CSV upload - but you gotta be stupid careful doing it
c
I've seen performance issues. sometimes a customer just wont load
a
Gotcha - appreciate it guys, these are the things I have loose memories of hearing too but never really seen serious issues in the wild myself so wanted the clarity.
@KevinJ of Kansas which drop-down is capped at 25?
k
Address list - for actually editing them from the customer record
a
ohh i think i get what you mean now
k
It might be 50. either way, when you start talking more than a hundred addresses you literally can't find them to make changes
And there's no way to re-sort/filter it
And you can't edit the address from a list/other page
a
I'm editing a customer right now with 849 addresses, and it looks like I can paginate to all of them and edit any one I want - also, I can switch the view to "All" and see them all in edit mode
Maybe it was fixed?
OK but clicking edit on any of them appears to be a crapshoot, and super buggy
Interestingly, it seems to consistently work fine if I click the address row to select it before clicking the Pencil/Edit icon.
j
Worked with an environment where a single account reached 250,000 addresses. At that point performance went poop. Anywhere under that should be fine.
k
That's not the problem. The problem is Finding the address to edit it
💯 1
netsuite 1
Load a thousand addresses on the record. Make them kinda close to each other. Then try and find address # 369 from your list by looking at it
Then add an address a second time on the customer because you can't find the first one. Now you've got 1 good and 1 bad address that are super close
It's not about the process of physically editing it - that's fine. The problem is it's a one directional load. You make a typo in your address? Good luck getting back to it to fix it.
I'll give you an example: T-Mobile has like 2000 stores all across country right? The thing is these stores get rennovations and many of them are in malls and you get instances where "oh this one isn't in suite 400 anymore it's in Suite 200" - that's where the stupid number of addresses become a problem.
Or your customer is terrible about giving you valid address information because they are building their address database before they have a physical address, because... construction
Had this problem with t mobile as a customer at 2 different clients
j
exactly, it got so bad we could not even load up the customer to enter an order. Customer Service did not edit addresses, they entered new ones if they did not exist.
a
ah gotcha - yeah they would need to add standard sublist functionality to the address sublist so you could search it perhaps - or/also make addresses indexed as part of global search
k
You can't get to the address to edit it that way - that's the problem
👍 1
Open in Slack
PreviousNext
Powered by