I really wish they would make the primary bin a database field.
I get so many requests to query this data and it’s such a pain in the butt to need to make it use the BO on GetList to populate a field. BAH.
#EndRant
Maybe I’ll just make it a UD field…
Yeah in some cases we have a _UD Field and in Data Directive we just populate that UD Field with the temp information so we can stop chasing it.
Just curious … Where (or better yet, How) is the Primary Bin value stored?
Well–that’s not intuitive at all.
And field help is useless for that.
They explain why they have that table.
Wellllll fine.
#UnjustifiedRant.
When I need to find a field, I use the Help File that @hkeric.wci (I think?) made. You can use it like a searchable data dictionary
What happened to “you’ll just know!”… sigh
So DB structures are like porn?
“Hard to define, but you know it when you see it”
I plead the fifth.
Shame, indeed. I was even at your Insights presentation. LOL
I think you can also go blind looking at them…
Another thing I do is I have installed CMDER on the Server then I can grep server binary files and then I know which ones to use .NET Reflector or on the Client.
Example - Client Side Only:
What it indicates is that there is a Method, Class or String matchin the text
Lets search for an Error or Warning String
Lets see who has something with Negative*Quantity
Lets see who has something with OrderHed.PONum within the Client Adapters/UIApps etc…
It helps knowing which DLL to .NET Reflect on or JustDecompile.
You can also map the UNC Path of Server Assemblies to a Drive Letter and use it from your PC. By the way grep is FAST and I mean fast, once it caches your directory you get instant results.