I have a problem. Using super solution Workflow Elements by Aiden Kaskela I create a workflow in crm365 dynamics, which sends emails with attachet document. The document is created dynamically from a word template. The solution works correctly in the entity Quote -email with attachment is sent correctly. Identical flow associated with Sales Opportunity Products sends an email without attachment, although the process also does not report any errors. What settings and conditions may affect this situation? I noticed that OpportunitProduct is not "active" - I can't set OpportunitProduct entity in Target at the Attach step. Unfortunately, I have nine options to switch this setting for OpportunityProduct. Is there any way solve this problem? Question two: Is it possible to pass the parameters to the child workflow? I could initiate a schematic from the product and pass the ProductOpportunityID parameter to child workflow Opportunity. Then I would build a document just for this Product only in the child's workflow. I have a problem. Maybe you'll want to help me. Using your super solution Workflow Elements I create a workflow in crm365 dynamics, which sends emails with attached document. The document is created dynamically from a template. The solution works correctly in the entity Quote -email with attachment is sent correctly. Identical flow associated with Sales Opportunity Products sends an email without attachment, although the process also does not report any errors. What settings and conditions may affect this situation? I noticed that OpportunitProduct is not "active" - I can't pin to it and enter OpportunitProduct entity in Target at the Attache step. Unfortunately, I have nine options to switch this setting for OpportunityProduct. Is there any way around this problem? Question two: Is it possible to pass the parameters to the child workflow? I could initiate a schematic from the product and pass the ProductOpportunityID parameter to child workflow Opportunity. Then I would build a document just for this Product only in the child's workflow.
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.