Thanks for the clarification @Eklon Eleuterio. Can you describe the steps you took to use 2 different datasets on separate Workbook visualizations (tabs)? As far as I know, you can only use one common dataset across the visualizations (tabs) unless you link a second one through dataset linking. -Jack

Thanks for the update @Rizkygaus. In that case, mark the Enable Logging checkbox and set the Keep Instance and History field to Always in the Workflow Definition page. See the sample screenshot below: After doing the above steps, process a Bill Payment again and the logs should then show up. -Jack

Thanks again for the update @Eklon Eleuterio. Kindly check the following additional items if they will resolve the errors you are getting: 1. On the workbook definition screen, make sure that the visualizations that use 2 datasets have those datasets listed under the Dataset section, and that they are linked with the…

Hi @Rizkygaus, Do you still need further assistance with this concern? If so, we would appreciate you providing the additional information we were requesting in the previous post. -Jack

Hi @User_1AF8B, Have you already contacted NetSuite Customer Support about this issue? We would appreciate an update from you. -Jack

@Eklon Eleuterio, I was able to successfully deploy a project with a workbook associated with 2 datasets by saving the workbook and exporting the XML file again for that workbook. See my deployment log below: With that said, the XML file for your workbook might be outdated so, you would need to export the file again from…

@Eklon Eleuterio, looking further into this, you are correct that associating 2 datasets to one workbook is now possible using the Dataset linking feature that was released in version 2022.1. Thanks for pointing this out. With that said, allow us to do more tests on how we can successfully get SDF to work with the object…

Thank you for the clarifications @rburns515. To set proper expectations, please be informed that the scope of our support here in the NetSuite Support Community does not include creating and implementing any complete custom solutions such as custom records and approval workflows from scratch since it requires analysis of…

Sorry, I'm still a bit confused about your requirement. So, you do not have the parts request and approval workflow set up in NetSuite yet? Also, is the workflow to be used for project approval or parts request approval? -Jack

@Eklon Eleuterio, I can see that you already have an associated workbook with custdataset_zup_dataset_importacoes_impostos.xml. But it is missing for custdataset_zup_dataset_cronograma_importa.xml. Take note that a workbook can be paired with a single dataset only. If you don't have a workbook yet for the dataset indicated…

Just to confirm if I understood your inquiry, you seem to imply that you already have the Parts form already set up in NetSuite and you only need to confirm whether the Parts form/records created by your Sales Reps are tied to an approval workflow. Is this correct? -Jack

Greetings @rburns515, You can see the list of Workflows deployed to your Parts Request record, including the approval workflow in question on the Scripted Records page. To access the page, navigate to Customization > Scripting > Scripted Records > Click the View or Edit link for the Parts Request record > Click the…

Greetings @John Robertson Sr., Looking at your Workflow setup, here are the adjustments that you need to perform to make it work: 1. On the Condition of the Set Field Value Action, since you will be checking the value of the field on the current record, keep the Record column blank and select the Exclude Commissions in the…

I think that is a good idea, and based on my testing, it should work, including the direct setting of the Lead to inactive! Thank you for sharing that idea @Alessandro A 🙂 -Jack

@Eklon Eleuterio, it seems that we are almost done 🙂 Based on the new validation log you provided, the cause of the error this time is that there are no Workbook XML files in the project associated with the dataset XML files, custdataset_zup_dataset_cronograma_importa.xml, and…

Thanks for confirming @Rizkygaus. I checked your workflow setup and it seems that you have configured the Set Field Value action under the Approved State correctly. To troubleshoot further, on the Bill Payment record that did not change the status upon clicking the Approve button, kindly check which state the approval…

@Benjamin Paul - USA, I think the real question here is why did period and documentstatus IDs worked in the first place. They are not supposed to work in SuiteScript since the records browser suggests different IDs for the fields in question. The case here could be an outlier since it has not been observed in other…

Greetings @Alessandro A, Thank you for posting a new inquiry here in NetSuite Support Community. To answer your question, a Workflow can only address the creation part of your requirement with the Create Record Action. Currently, it is not capable of performing the elimination part since Workflows cannot delete records…

Yes, as suggested in #1 in my previous post, the highlighted part below should be the only dependency in the manifest: The <objects></objects> part should be removed. Also, you might need to export the XML file for custdataset_zup_dataset_cronograma_importa from the source account and add it to the project since the…

Greetings @Gabriel Jarillo Soto, I was about to reply to you with a similar answer. But, here is the formula that we would suggest: Take note that there is a timezone conversion included. For more details, see my published Admin Tip linked below: https://community.oracle.com/netsuite/english/discussion/4477741 -Jack

Hi @Eklon Eleuterio, Thanks for the update. I think we are close to solving this one. Can you try the following additional adjustments to resolve the errors you are getting: 1. In the manifest.xml file, only include the dependency indicated in the screenshot below and delete the others. 2. I noticed that you have 2…

Greetings @User_1AF8B, Since the issue described here is resolved on a case-by-case basis, it is recommended to file a case to NetSuite Customer Support, as they have the tools to investigate and analyze these issues. Let us know if you need assistance with case filing. -Jack

@Charles B, thank you for clarifying and apologies for the confusion. I have edited my comment to imply that there might be fields that are not yet supported. So, if a field is not yet listed in the Field dropdown on the Set Field Value Action, it might be not yet exposed to Workflows and you may need to use SuiteScript…

Hi @Charles B, Thanks for joining in the discussion here. To learn about setting sublist fields in Workflows, see the following resources: For Supported Client Triggers: For Server Triggers: SuiteAnswers Article 70217: Using Sublist Action Groups WEBINAR REPLAY | Automate Business Processes Using Set Field Value Workflow…

Hi @b2wise, Testing on this, it appears that you are correct with the behavior you described and I also reproduced it on my end. So, as a correction to my previous statement, only Summary Search-derived Non-Stored Custom Fields are not available in Saved Search results, and Formula-based Non-Stored Custom Fields are not…

Thanks for confirming @Eklon Eleuterio. Upon further testing, here are some steps and adjustments that you need to perform to successfully validate and deploy SDF Projects containing Workbooks, Datasets, and Translation Collections: 1. The Workbook, Dataset, and Translation Collection XML files must be in the Objects…

Thank you for providing the case details @CJ Carter. We would appreciate it if you provide updates here on the case resolution as it will be helpful as well to others who encounter the same issue. -Jack

Greetings @User_XNGDV, Thank you for posting a new inquiry here in NetSuite Support Community. Our gurus who specialize in this subject will look into your inquiry and will get back to you with an update. To other members who have any ideas, feel free to share them here. -Jack

Greetings @Vernita, Thank you for posting a new inquiry here in NetSuite Support Community. Our gurus who specialize in this subject will look into your inquiry and will get back to you with an update. To other members who have any ideas, feel free to share them here. -Jack

Hi @CJ Carter, Thanks as well for the update. The issue here could be a potential defect. So, it is recommended to report it to NetSuite Customer Support by submitting a case so that they can investigate further. Let us know if you need assistance with case filing. We would also appreciate it if you can provide the case…