Has anyone noticed in 2025.2 address data is not being picked up correctly for customers via suiteql?

Curious in what way it's wrong? And is this truly only in SQL or is it also via the ODBC?

I had a previous join which is no longer pulling data, I’ve had to change the join

@Ritesh Mistry What did you end up changing. I've just noticed this for one of our integrations which was doing a join to get customer billing addresses

@John Ferlito are you retrieving data from the transaction table?

@Ritesh Mistry Yes it's a join against transaction

Do you want to share your SQL @John Ferlito , dm me if you prefer to share privately

Actually I'm querying customers. The query that was working fine before is. Im using ksley as an ORM let me know if you need the raw SQL

const customerQuery = db
  .selectFrom('customer')
  .leftJoin('employee as salesrep', 'salesrep.id', 'customer.salesrep')
  .leftJoin('term', 'term.id', 'customer.terms')
  .leftJoin('currency', 'currency.id', 'customer.currency')
  .leftJoin('customeraddressbookentityaddress as billingaddr', 'billingaddr.nkey', 'customer.defaultbillingaddress')
  .select((eb) => [
    'customer.id',
    'customer.entityid',
    'customer.companyname',
    'customer.email',
    eb.case().when('salesrep.id', 'is not', null).then(sql<string>`salesrep.firstname || ' ' || salesrep.lastname`).else(null).end().as('salesrepname'),
    'term.name as paymentterms',
    'currency.symbol as currency',
    'billingaddr.addr1 as billingstreet1',
    'billingaddr.addr2 as billingstreet2',
    'billingaddr.city as billingcity',
    'billingaddr.state as billingstate',
    'billingaddr.zip as billingpostcode',
    'billingaddr.country as billingcountry',
  ]);

Interestingly though somethign as simple as this returns no rows (not sure if it did before)

SELECT * FROM customeraddressbookentityaddress

Fascinating, that is the exact issue I had

Hmm interesting. I wonder if it's a bug or just a permission change. I couldn't see anything in the release notes nor any permissions that made a difference

I think it’s a bug or a silent deprecate