Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support nullFieldList #398

Closed
iloveitaly opened this issue Jun 19, 2018 · 1 comment
Closed

Support nullFieldList #398

iloveitaly opened this issue Jun 19, 2018 · 1 comment

Comments

@iloveitaly
Copy link
Member

For fields, including customFields, you cannot pass Null values or empty tags to the NetSuite API. The proper way of deleting a value from a certain field, is to add it to the nullFieldList (which is a separate element within the request profile). Note, you insert the name of the element you wish to blank out here. In the case of customFields, you should use the NetSuite internal ID, not the human readable name from the profile

https://system.na1.netsuite.com/app/help/helpcenter.nl?fid=section_N3527090https://system.na1.netsuite.com/help/helpcenter/en_US/Output/Help/section_N3438152.htmlhttps://system.na1.netsuite.com/app/help/helpcenter.nl?fid=section_N3438152
cgunther added a commit to cgunther/netsuite that referenced this issue Feb 24, 2022
@cgunther
Add support for NullFieldList (starting with invoices)
5e181d9 
NullFieldList is used to either clear an existing value on update, or
avoid a default being applied on adding a record.

My use case only required support for invoices, so I started there, but
this could likely be added to most records.

This was heavily inspired by @gmike11's work in NetSweet#481, but that seems to
lump a bunch of changes together. This also solves NetSweet#398.

Where NetSweet#481 manipulated the XML request body to address that the
`<platformCore:nullFieldList>` needs to always use the `platformCore`
namespace, as opposed to the records normal namespace (ie `transSale`
for invoice) as happens for any other field, I tried to address that on
the `#to_record` side.
cgunther added a commit to cgunther/netsuite that referenced this issue Feb 24, 2022
@cgunther
Add support for NullFieldList (starting with invoices)
a52d097 
NullFieldList is used to either clear an existing value on update, or
avoid a default being applied on adding a record.

My use case only required support for invoices, so I started there, but
this could likely be added to most records.

This was heavily inspired by @gmike11's work in NetSweet#481, but that seems to
lump a bunch of changes together. This also solves NetSweet#398.

Where NetSweet#481 manipulated the XML request body to address that the
`<platformCore:nullFieldList>` needs to always use the `platformCore`
namespace, as opposed to the records normal namespace (ie `transSale`
for invoice) as happens for any other field, I tried to address that on
the `#to_record` side.
cgunther added a commit to cgunther/netsuite that referenced this issue Mar 31, 2022
@cgunther
Add support for NullFieldList (starting with credit memos and invoices)
19d5c24 
NullFieldList is used to either clear an existing value on update, or
avoid a default being applied on adding a record.

My use case only required support for credit memos and invoices, so I
started there, but this could likely be added to most records.

This was heavily inspired by @gmike11's work in NetSweet#481, but that seems to
lump a bunch of changes together. This also solves NetSweet#398.

Where NetSweet#481 manipulated the XML request body to address that the
`<platformCore:nullFieldList>` needs to always use the `platformCore`
namespace, as opposed to the record's normal namespace (ie `transSale`
for invoice) as happens for any other field, I tried to address that on
the `#to_record` side.
@cgunther cgunther mentioned this issue Apr 6, 2022
Merged
cgunther added a commit to cgunther/netsuite that referenced this issue Apr 6, 2022
@cgunther
Add support for NullFieldList (starting with credit memos and invoices)
2a416eb 
NullFieldList is used to either clear an existing value on update, or
avoid a default being applied on adding a record.

My use case only required support for credit memos and invoices, so I
started there, but this could likely be added to most records.

This was heavily inspired by @gmike11's work in NetSweet#481, but that seems to
lump a bunch of changes together. This also solves NetSweet#398.

Where NetSweet#481 manipulated the XML request body to address that the
`<platformCore:nullFieldList>` needs to always use the `platformCore`
namespace, as opposed to the record's normal namespace (ie `transSale`
for invoice) as happens for any other field, I tried to address that on
the `#to_record` side.
iloveitaly pushed a commit that referenced this issue Apr 7, 2022
@cgunther
Add support for NullFieldList (starting with credit memos and invoice…
6c81f30 
…s) (#529)

NullFieldList is used to either clear an existing value on update, or
avoid a default being applied on adding a record.

My use case only required support for credit memos and invoices, so I
started there, but this could likely be added to most records.

This was heavily inspired by @gmike11's work in #481, but that seems to
lump a bunch of changes together. This also solves #398.

Where #481 manipulated the XML request body to address that the
`<platformCore:nullFieldList>` needs to always use the `platformCore`
namespace, as opposed to the record's normal namespace (ie `transSale`
for invoice) as happens for any other field, I tried to address that on
the `#to_record` side.
@iloveitaly
Copy link
Member Author

fixed with #529

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@iloveitaly