There's no limit in the sense that TRIM will let you add as many as you want...
However, we've got a site that reached half-million items in a set... they paid HP Professional Services to create a customised tool or add-in to make it work without killing TRIM and everything else around it, so you could potentially buy the same solution.
On the other hand, 50,000 is no where near 500,000 and it may work fine.
:::::::::::::::::::::: NOT A HP EMPLOYEE ::::::::::::::::::::::
50,000!?!?!?! I would agree that it's unreal for a lookup set to have that and would seriously question the need for it. Sounds to me that there's not a lot of "structure" being managed for your records management (I think that you agree that it's too much).
You might want to have a "justification meeting" to see if those couldn't be reduced.
They want a lookup set that will be a list of property addresses. The first part will be a property ID, which they will always know. The rest of the string will be the actual address. Hopefully it won't be too bad - all they need to do is enter the number and auto-select should pick up the rest of it.
After the system goes live, it is intended to integrate TRIM to the application that holds the source information(unless we can can change their minds and do it now).
Sounds as though it should work for the time being, if a bit clumsy.
Given the purpose of the lookup set, you could use locations (specifically the location type Venue).
You can then setup a additional field of type location. In 7.2, you can limit these additional fields to be Venues only.
That way, you'll prevent using that massive lookup set and have "free" searching capability in the locations table without the need for custom development and you have your property information structured in a location object.
(Any opinions expressed in this forum are my own personal opinion and should not be construed as an official statement by DXC Technology.)
Analytics & Data Management Application & Business Services DXC Technology