Hello <@U2QGK3FA5>, please read <https://nlcorp.ap...
# sdfa
Albert Margarit (NS Eng Lead)
05/29/2019, 10:08 PMHello @SuiteBender, please read https://nlcorp.app.netsuite.com/app/help/helpcenter.nl?fid=section_1528397245.html. You can override the default behavior for Account Specific Values. By default is to stop the process, however, you can choose to throw a warning instead and still proceed with the deployment
b
bputnam
06/04/2019, 4:00 PMHi @Albert Margarit (NS Eng Lead) and @SuiteBender Here are a couple of screenshots showing that after I clicked add dependencies to the manifest, not all dependencies were captured and after trying to validate the project it points to another dependency and I manually add it to the manifest file and I’m able to now validate and deploy. Is there a specific reason why are some dependencies not automatically added? On my next post I’d like to show that even after manually adding the dependencies exposed by the validation against the account it finds new unaccounted dependencies during a failed deployment that are not exposed during the automatic “add dependencies to the manifest” and the ones exposed during “validate project against account”.
a
Albert Margarit (NS Eng Lead)
06/05/2019, 7:29 AMHello, thanks for providing examples. We are currently under heavy refactoring of the add dependencies functionality and should definitely check these cases.
👍 1
Albert Margarit (NS Eng Lead)
06/05/2019, 7:32 AM@Luis Pérez Villegas (NS Devtools SE) can you take a look at these cases?
l
Luis Pérez Villegas (NS Devtools SE)
06/05/2019, 12:50 PMHi @bputnam.
As Albert mentioned, we are working at this very moment in improving the validation and management of manifest dependencies (list missing dependencies, add dependencies, etc)
So, thanks for your feedback, it's very valuable!
Could you please send us a screenshot of the xmlfile where you are referencing those missing dependencies? It will help us to identify exactly what's happening in your case.
b
bputnam
06/05/2019, 3:20 PMThanks for the response guys. Yes I can do that but do you mean the manifest xml? or the actual custom record xml?
bputnam
06/05/2019, 4:43 PM@Luis Pérez Villegas (NS Devtools SE) sent!
l
Luis Pérez Villegas (NS Devtools SE)
06/07/2019, 1:47 PMHi again! I have already checked the files and found that we have already improved this message. We will propagate the correction for the next release.
So, the message was misleading, because the error could be due to the file missing in the project or the dependency reference missing in the manifest.
However, in reality, the error message you are facing now should be the following:
Invalid "sourcefrom" reference key "[scriptid=customrecord_pup_deal_sel_job.custrecord_pupds_job_date]"
What this message means is that the reference is wrong. <sourcefrom> label doesn't have to refer to an object/xml file but to a value like STDBILLINGACCOUNTBILLADDRESSLIST or STDTIMEPRODUCTIVE...
Hope it helps
b
bputnam
06/10/2019, 5:33 PMWhat if my sourcing is dynamic? I would have to push a constant value in the sourcefrom tag and them edit in the UI to source my dynamic value? and I can see how deleting the value from the sourcefrom tag could help pass validation but unsure about the first question
bputnam
06/10/2019, 5:34 PMdoes SDF not currently support dynamic sourcing from other records?
l
Luis Pérez Villegas (NS Devtools SE)
06/12/2019, 1:49 PMHello again! I'm not completely familiar with your problem, but I guess you should have to change them manually in the UI as you suggested.
I will consult with my colleagues but to my knowledge there is no support nowadays to dynamic sourcing.
b
bputnam
06/19/2019, 3:33 PMHi Luis. The problem is as I mentioned. When I have a custom record that contains a field that has dynamic sourcing from another record/field SDF is unable to add its dependency to the manifest and I can’t move the object from one instance to another without manually fixing it by using a constant in the xml and going to the UI and re-adding my sourcing
bputnam
06/19/2019, 3:35 PMI am now pasting screenshots of my 2nd issue. Which is, my project does not add all dependencies when I ask it to add dependencies to the manifest. I try to do validation and it exposes other dependencies. I manually add them to the manifest and it passes validation! Now, on the last step I try to deploy to my desired account and it finds new dependencies that do not allow me to have a successful deployment even after passing validation.
bputnam
06/19/2019, 3:38 PMmessage has been deleted
bputnam
06/19/2019, 3:38 PM@Albert Margarit (NS Eng Lead) @Carlos Olivares (NS DevTools PM) @Luis Pérez Villegas (NS Devtools SE)
l
Luis Pérez Villegas (NS Devtools SE)
06/19/2019, 4:14 PMHi Again! About your 1st issue, I can confirm you that sdf doesn't support dynamic sourcing at this moment. That means that the tag <sourcefrom> can only take specific values and not references to any Object.
Luis Pérez Villegas (NS Devtools SE)
06/19/2019, 4:30 PMAbout the 2nd one let me break into two parts.
a) About not adding all dependencies. Can you pass me the screenshoot of the result of add dependencies?
b) About the last validation, I'm afraid the last message is not asking you to add dependencies, but it is an error located in customrecord_acq_lot_cert_entry.xml or in customrecord_acq_lot_cert_entry.custrecord_lot_cert_deal
Take into account that when you use the command "validate" is only validating locally in your machine.
There are some validations that are only made server-side (this case) so it's possible they don't appear if you execute command "validate" but appear as an error when executing other commands.
If you want to validate servers-side you should execute the command "sdf validate --server"
2 Views