We're starting to observe an issue with SuiteApp C...
# sdfd
darrenhillconsulting
07/24/2021, 12:18 PMWe're starting to observe an issue with SuiteApp Control Center deployments. When we create a new version and a customer updates, the value in existing custom fields are wiped out on the update. Obviously we can't have this. Is there a setting or config that we're missing that would prevent this?
a
Ali Syed (NS DevTools QA)
07/24/2021, 12:51 PMHi, what do you mean by "when customer updates"
Can you please provide a step by step example. I will check with check with concerned team but i will need more info.
d
darrenhillconsulting
07/26/2021, 2:27 PM1. We create a v1.0.0 of a SuiteApp that contains a custom field on an Item record.
2. Customer installs v1.0.0, sets a value on the Item record's new custom field
3. We release v1.0.1 (still contains the item custom field)
4. Custom upgrades to v1.0.1, the value they previously set (in set #2) gets wiped out (blanked)
darrenhillconsulting
07/26/2021, 2:27 PMThat's is @Ali Syed (NS DevTools QA)
a
Ali Syed (NS DevTools QA)
07/26/2021, 2:30 PMOk, we are working on something which will be delivered in upcoming release.
Without getting too much in detail: You will have control via installation preferences to tell SDF, when a customer updates the suiteapp, what should be the behaviour for some specific objects/ or all specific objects. (Either respect whats being delivered by author (you), or respect what value has been set by the user.)
Ali Syed (NS DevTools QA)
07/26/2021, 2:30 PMBut it will be limited for only
Script Deployments
Custom Record Instances
Custom list values
Ali Syed (NS DevTools QA)
07/26/2021, 2:32 PMBy the way which is the account version of NS where this problem was observed.
d
darrenhillconsulting
07/26/2021, 2:40 PMI'm confused a little ... this is a big deal no?
a
Ali Syed (NS DevTools QA)
07/26/2021, 2:46 PMYes it is, but keep in mind it will not be applicable for all object types.
For now its already available for script deployments in overwriting XML,
And 2 more (instances of custom records, and custom list values)
I am not sure if your use case regarding custom field falls under that category.
Ali Syed (NS DevTools QA)
07/26/2021, 2:47 PMBut what you have described, it seems like a bug, it should never leave the field empty for user after update.
The expected behaviour is that field should be reverted to the original value described in suiteapp.
d
darrenhillconsulting
07/26/2021, 3:11 PMOk, even that is scary then. If I have a custom item field (let's say a text field) that the customer populates, and a new SuiteApp version is released ... that upgrade will remove (blank out) that value. Its a showstopper
f
fkrauthan
07/26/2021, 8:20 PM@darrenhillconsulting do I understand this correctly you have a customfield on a netsuite record and on plugin update the value the user entered gets cleared?
d
darrenhillconsulting
07/26/2021, 10:26 PMnot
pluginSuiteAppf
fkrauthan
07/29/2021, 10:41 PMsorry I ment SuiteApp. Ok that is scary as hell. netsuite currently pushes us to switch but this would be an absolute show stopper
a
Ali Syed (NS DevTools QA)
07/29/2021, 11:23 PMPlease open a NS support case, so it can be officially documented.