I'm looking at a transaction search here that uses...
# suitescript
c
I'm looking at a transaction search here that uses customerMain as a search join and its failing in some accounts but not all. customer is also a valid search join and thats what the failing accounts appear to want. Why would 1 account work with customerMain and one only with customer? is this a bug or am I just going crazy today?
j
Is there a difference where the customer is a company vs an individual?
c
customers in multiple accounts are of type "Customer" so there does not appear to be a difference
m
What types of transactions in this search?
c
straight up invoices
m
You’re searching in script @creece and for whatever reason, you can’t join through entity?
c
yeah there's an existing search and it uses customermain.entityid and it bombs out w/ customermain... in the accounts it works in customer (main) is available in a search filter criteria but in the accounts its messing up in, customer (main) is not available and just customer (fields) is available
not sure why the 2 accounts would be different when its the exact same bundle.. it smells like a ns bug but there may just be a setting somewhere
im admin in both scenarios and runs as admin
so its not permissions
m
It’s clearly a feature that needs to be enabled.
Ah…
Answer id 81209
If projects are enabled, you need customer main
You can use
N/runtime.isFeatureInEffect
to branch your logic around projects.
c
if only it was in 2.0 lol thanks man i'll take a look at this real quick
+1million internet points to you...i searched all over suiteanswers i swear you gotta get the exact phrase or it just doesn't give you what you want
m
Yeah, I’ve been trying different things throughout the day as I had time. Finally got lucky.
c
def appreciate it.. that should answer that one.. .i knew it was something simple
m
No problem. I love getting random puzzles fed to me throughout the day. It’s why I love my job.
c
do you know what you searched to find that
m
“customer (main) enable feature”
💯 1