With 2026.1 under my integration role I can no lon...
# ask-stanley-ai
t
With 2026.1 under my integration role I can no longer execute the SuiteQL joining EntityAddress it doesn’t error out it just returns an empty result set. Administrator it works but not sure what new permission is necessary to read the EntityAddress. If I comment out all of the address stuff it works great. My FROM clause reads like this:
Copy code
FROM
	Transaction
	INNER JOIN Vendor ON (Vendor.ID = Transaction.Entity)
	INNER JOIN TransactionLine ON (TransactionLine.Transaction = Transaction.ID)
	LEFT OUTER JOIN EntityAddress AS VendorAddress ON (
		VendorAddress.nkey = Transaction.BillingAddress
	)
c
AI generated answer (using internal Slack threads):
Based on the conversations, it seems that the issue you're facing is related to the permissions of the integration role you're using. In NetSuite 2026.1, there might have been changes in the permissions required to access certain tables or records, such as the EntityAddress table. However, it's also important to note that the EntityAddress table is not directly joined with the Transaction table. Instead, it's joined through the EntityAddressbook table. The EntityAddressbook table contains a field called
AddressBookAddress
which is the
nkey
for the EntityAddress table. Here's an example of how you can join these tables:
Copy code
sql
SELECT
    Transaction.ID,
    Vendor.ID,
    TransactionLine.ID,
    VendorAddress.*
FROM
    Transaction
INNER JOIN Vendor ON (Vendor.ID = Transaction.Entity)
INNER JOIN TransactionLine ON (TransactionLine.Transaction = Transaction.ID)
LEFT OUTER JOIN EntityAddressbook AS VendorAddressbook ON (VendorAddressbook.Entity = Vendor.ID)
LEFT OUTER JOIN EntityAddress AS VendorAddress ON (VendorAddress.nkey = VendorAddressbook.AddressBookAddress)
In this query, we first join the Transaction table with the Vendor table. Then, we join the TransactionLine table. After that, we join the EntityAddressbook table where the Entity field matches the Vendor ID. Finally, we join the EntityAddress table where the
nkey
matches the
AddressBookAddress
from the EntityAddressbook table. If you're still not getting any results, it's possible that the integration role you're using doesn't have the necessary permissions to access the EntityAddressbook or EntityAddress tables. You might need to adjust the permissions of the role or use a different role that has the necessary permissions. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******
Slack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.829650879
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.812805057
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.810424805
Please provide your feedback on this answer.
t
That same SQL query works great unchanged using Administrator in 2026.1 and my integration role in 2025.2. I could change the SQL but still feel it’s a permission issue for sure. So do you know the specific permission I need to add to my integration role?
That same SQL query works great unchanged using Administrator in 2026.1 and my integration role in 2025.2. I could change the SQL but still feel it’s a permission issue for sure. So do you know the specific permission I need to add to my integration role?
a
i was facing same issue. After some R&D i came to know, Now there are separate separate tables for billing and shipping addresses. plz use them now