Hi all, has anyone else found this, I am deploying PDF templates, to a production account. when it deployed it didn't deploy against the record they were against, instead they deployed as pictured. You can not edit them they just error with

An unexpected error has occurred. Please click here to notify support and provide your contact information.

I then created it manually in the UI and downloaded the XML I found that the opening XML had change from

<advancedpdftemplate scriptid="custtmpl_sf_packing_slip" standard="STDTMPLEMPTY">

to

<advancedpdftemplate scriptid="custtmpl_sf_packing_slip" standard="STDTMPLPACKINGSLIP">

so I updated the files in the SDF project to try and unlock the erroring records and then I get this error

An error occured during validation of Custom Objects against the account (custtmpl_sf_packing_slip)
Details: The standard attribute value, STDTMPLEMPTY, cannot be modified.
File: ~/Objects/custtmpl_sf_packing_slip.xml

Has anyone else had this issue and found a way around it?

Hi, I am trying to deploy an e-mail template but receives below error even if I have the non-empty template xml file in the same folder. Have also tried to include the template in the deploy.xml file. Anyone knows how to solve it?

<objects>
  <path>~/Objects/custemailtmpl_templatename.template.xml</path>
  <path>~/Objects/custemailtmpl_templatename.xml</path>
</objects>

An error occurred during custom object validation. (custemailtmpl_templatename) Details: Provide a non-empty template file.

Hi All! Currently, i am setting up my Eclipse Mars to develop Scripts for netsuite but i am receiving an "Two Factor Authentication required" error? How to fixed this? I already enabled the 2FA on the role assigned to my account

See this thread

I would also love to know whether suitecloud project:adddependencies is working fully all the time. We're using the cli tool to deploy continuously, and it's sometimes the case that not all dependencies are added to the manifest even though deploy.xml has all the source objects listed. This breaks the automated deploy requiring manual addition of some objects to the manifest. One example would be with body fields, having a sourced field value, that's one case where validation ran but did not add all dependencies. Has anyone experienced similar?

With recent update of 2020.2

importbundle

is failing with sdfcli

sdfcli importbundle -authid auth_dev -bundleid BUNDLE_ID -p /.sdfoutput

. This does not happens in every bundle, but some bundles are failing. I am using sdfcli for java, PLMK if anyone else is experiencing similar issues or could be due to any specific component in the bundle.

Is the SuiteApps app-listings very slow to filter and select page for everyone? (the SuiteApps tab inside of Netsuite, not suiteapp.com)

My client has this Project in GITHUB which was developed by their previous employee. I use Webstorm for the development but the only structure Webstorm has FileCabinet and and Objects. Just trying to understand what was the developing environment for this structure

this is likely something the previous employee just invented themselves.

^ this.

@stalbert make sense. Thanks

I'm setting up a suiteapp with webstorm and the project contains three custom records that are totally self contained (no references to standard records). Add to that there are three scripts. When I run the add dependencies function in webstorm, it adds WMSSYSTEM. I don't have anything related to it... When I deploy it without that dependency, it deploys fine. If I have that dependency included, it won't deploy because of missing dependency for the account. Is there some way of seeing what triggered the addition of a specific dependency?

Does SDF fully analyze dependencies included in a project prior to deploy? I'm running into the following problem: * SDF project has a script definition with a script param pointing to a saved search * said saved search is in the SDF project upon deployment, I get an error saying the saved search referenced in the script deployment can't be found? I thought SDF was smart enough to look in the project and deploy things in the necessary order? i.e. if the search is a dependency by virtue of it being indicated in a script parameter, that the search would get deployed first, automatically?

my workaround was to comment out the script from the SDF project deploy.xml, then deploy just the search, then uncomment the script and reploy again.

That is a deal breaker in any project with dependencies as I describe above. If it can't determine an order of deployment intelligently for the contents of itself what's the use?

Perhaps you can explicitly deploy the saved search first in your deploy. Still annoying, but a workaround.

rather than commenting one out

I tried that and it didn't seem to work - it still seemed to go for the script first, searches second even though the searches were moved above the script in

deploy.xml

ah, interesting

so unless I forgot to save the file, the top down order in

deploy.xml

doesn't seem to strictly drive things - and I really hope it doesn't as I thought SDF was supposed to sort out intra-project dependencies as part of the value add of the tool?

ironically, a coworker brought up the issue the other day- I have never seen a problem with 'ordering' of objects and assumed SDF was intelligently ensuring dependencies in the project were deployed before things that depend on them.

i was skeptical, but now seeing this fairly simple case of [script/deployment->depends on a search in the current project] failing due to the dependency not being found make me think that coworker's concerns are legit.

maybe this is a small gap and SDF actually does analyze dependencies inside a project for all other cases where similar situations would arise?

Pretty sure we'll need some official responses here

Doubtful anyone else knows

@stalbert The script in question which is not found in the account while deploying, is it part of a suiteapp which is already in account? Or it exists in the project but sdf is not finding it? I am not 100% sure but if you have a dependency on a script which is part of another suiteapp, that might create the problem you are facing. If its part of your project then Sdf should resolve the dependency automatically and if this is not happening then its a bug. When you run add dependencies, it is adding the dependency in manifest? (In case your referenced script is in account and not in project)

With a custom record in SDF, is there a way to not overwrite the instance data?

I wouldn't expect any instance data to be overwritten unless you are explicitly including instance data within the definition.

I am, I'm using it as a configuration. I need certain records to exist but once in the account the values can change. I don't want the values overwritten on every update.

While I don't have a better off-hand suggestion, I'm not sure I'd use SDF to manage the initial instance, but since you're already there, you can probably now change the Instance definition(s) to use

ACCOUNT_SPECIFIC_VALUE

instead of the actual values