Mi contenido
Comentarios
-
Thanks, I've looked there (and oa_columns) It seems to be a standard field in netsuite.com, and appears in the general schema browser. https://system.netsuite.com/help/helpcenter/en_US/srbrowser/Browser2024_2/odbc/record/transaction_lines.html
-
Hi Francesca - I'm not sure I follow the reasoning there. The query I used above lists all fields, and there are definitely duplicated rows for some reason. There are no ids that are different, is there some semantics such as historic amendments/soft-deletions etc getting in the way here? I'll run using DISTINCT for now :)
-
In a similar way CompanyAddressbookEntityAddress is duplicating about 40 rows on nkey; identical fields between record duplicates. Q - Do I have to use distinct clauses to query all the Address entities because of systemic problems?
-
HI - thanks for the reply, at least I know the bug (enhancement!) is being tracked. Attendee isn't a field in that table, and response seems to be the only field that is has differences between duplicates. I'll use select distinct over all columns except response for now - I need all fields and I need to remove duplicates.
-
Thanks for the reply, listing just the IDs isn't what I want. I'm happy with my own findings - that entityStatus is equivalent to COMPANY_STATUS If this is categorically not the case, please do let me know.
-
There's no opportunity entity, but there is an entity opportunitiesAndEstimates which has the relevant fields denormalized for transaction of type Estimate / Opprtnty. Right now I'm just trying to create a set of views that look enough like netsuite.com to provide continuity on our reporting - so I think I've got what I…
-
It's TRANSACTIONS.COMPANY_STATUS_ID field, which used to be the FK to COMPANY_STATUS record on COMPANY_STATUS_ID in netsuite.com - as per the spreadsheet row I pasted. It looks like the notation in the spreadsheet "opportunity^transaction.entitystatus" is trying to say transaction.entitystatus → entitystatus.key for…