Mi contenido
Review our AI Community Guidelines before posting AI-generated or AI-assisted content. Verify accuracy and include the appropriate AI disclaimer.
Action Required: Review and submit pending reconciliation matches before the NetSuite upgrade to avoid rework. After 26.2, unsubmitted matches will be unmatched. For more details, see SuiteAnswers 1047397
Explore NetSuite Next with Free Training!
Build your skills with the LCS Explorer Pass.
Visit the NetSuite Next community page
to learn more, ask questions, and share your experience.
Build your skills with the LCS Explorer Pass.
Visit the NetSuite Next community page
to learn more, ask questions, and share your experience.
Comentarios
-
Ok, thanks. I only see three open/close <tr> tags in that piece of code: row 18 and 31 row 20 and 24 row 25 and 28
-
I apologize. Here is the source code. Edit: Attachment removed.
-
Hi there, Just looking for an update on this one. I even tried removing the footer and readding it but the error notice still appears when i try to generate a PDF print preview. Thanks!
-
Hi, This is a separate thread then the thread below. You can disregard that thread as we found a work around. https://community.oracle.com/netsuite/english/discussion/4479019 Attached is the source code for the template. Thanks!
-
Hello, Just checking on an update for this ticket. Im not sure how to locate the missing tr end tag. Thanks!
-
Hello, We found a workaround for this question. We just eliminated all the line breaks as formatting does not matter. Please disregard this question.
-
Well, Jack i think you did it. I tested three scenarios and they all generated and sent to the correct recipient! Well done! Thanks for your help and patience. I greatly appreciate it.
-
It does make sense. Below in yellow is where i added the additional set field value action, but two emails still executed when i tested a quote that contained both a price level 1-2 and price level 3-6. Im sure this is because the condition circled in blue below was met before the newly added set field value action, so…
-
Hi Jack, Maybe im not understanding. Highlighted below is the sublist action group for 3-6. I dont see a flag for 1-2, in any of the actions for 3-6. ?? Thanks!
-
Thanks Jack! The sublist actions worked! We are so close to wrapping this up! We have several price level ids with essentially two scenarios for items on the quote: If the line item has a price id is in list (x,x,x,x) as seen in the set field value, then it falls in to a price level range of 1-2 (see email flag name).…
-
Hello Jack, I really appreciate your help with this. I updated my formula with the internal id value you provided but the workflow log states line.price.id is not a found. I also tried price.level.id and received the same error and the email didnt trigger. Any other ideas?
-
Hi Jack, Thanks for the help however i still cant get my emails to send. Below is where i entered the check level formulas. We have many different price levels and business = 1 (appliance). Here is the workflow log for test EST/Quote 453 and you can see all the other workflow actions were triggered, except for the send…
-
Hi Jack, One more question. Is it possible for a workflow send email condition to reference an accounting list - price level like shown below? This is the item price level on the quote. Can i reference the highlighted price level field below in a workflow condition? As of now it is not an option. Maybe i missed a step.
-
ok, please disregard my second message as well. I added another workflow to keep today's date in the exp close date field whenever the other quote types are selected. Thanks for your help!!😀
-
Please disregard my previous post, it works now! Thank you! So one more thing, after i select either quote type contract builder or contract builder developer and the exp date changes as it should, is there a way for the date to go back to today's date if we select any other quote type? For example, if we select quote type…
-
Thank you. However when i copied this formula into the set field value action parameter, the exp close date in the quote is still returning 1/31/2022 and not a date 180 days in the future. For more information, the after field edit trigger is triggered on Quote Type. In the condition below, the Quote Type on the quote has…
-
I should also add that the workflow is using the client trigger "After Field Edit" on the quote expected close date field and is triggered off of "Quote Type".
-
Hi Jack, Im testing this now but i think you are on the right path!