Skip to content

Conversation

@cgunther
Copy link
Contributor

If you performed an advanced search specifying which columns to return and included externalId, you wouldn't be able to get the external_id from the resulting record via the usual external_id method. This now matches how internal_id is extracted.

Prior to this, calls to external_id returned:

> record.external_id
=> {:@external_id=>"customer_1"}

Now, it returns:

> record.external_id
=> "customer_1"

This originally surfaced in #470 as part of a larger change, but we're exploring taking that in a different direction, so extracted this out to it's own PR.

If you performed an advanced search specifying which columns to return
and included externalId, you wouldn't be able to get the external_id
from the resulting record via the usual external_id method. This now
matches how internal_id is extracted.

Prior to this, calls to external_id returned:
```
> record.external_id
=> {:@external_id=>"customer_1"}
```

Now, it returns:
```
> record.external_id
=> "customer_1"
```
@iloveitaly
Copy link
Member

Awesome fix! Thanks.

@iloveitaly iloveitaly merged commit ece6f61 into NetSweet:master May 31, 2021
@cgunther cgunther deleted the adv-search-results-externalid branch June 1, 2021 14:36
diegopolido pushed a commit to penrosehill/netsuite that referenced this pull request Oct 7, 2021
If you performed an advanced search specifying which columns to return
and included externalId, you wouldn't be able to get the external_id
from the resulting record via the usual external_id method. This now
matches how internal_id is extracted.

Prior to this, calls to external_id returned:
```
> record.external_id
=> {:@external_id=>"customer_1"}
```

Now, it returns:
```
> record.external_id
=> "customer_1"
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants