Forum Replies Created
-
Posts
-
Hi Alex,
This worked great. Instead of preparing the email during a rule, i had to create another rule that prepares the email. This rule had to be triggered from custom javascript. I called this rule after child item was created successfully. This way, the email had the newRecordLink variable populated and available.
Thank you so much for your help.
I got the flow and the separate list setup and working.
What i feel could be helpful from DFFS is that if we could avoid creating the email content from JS. Instead, if a rule can be used to be a placeholder with all the emails that needs to be scheduled, that would be great. Then in the js code, we will just have to reference the rule object, loop through all the emails, get all the email data and create a new record in the custom list. This will all have to be custom code, which I understand. But if we could create the emails in a rule to be referenced later, this would make it so much easier for future maintenances. I hope I am making some sense here.
In classic DFFS we were able to look inside the rule object from JS. With modern DFFS I see only rulestate and trigger rule options related to a rule. Do you think exposing rules and it’s related data to JS is a possibility?
Thank you,
Amal VellappillilThank you for the tip on _DFFSID column.
I know this is not possible now, but do you think in the future we can have something like this.
– Setup a rule with all the emails that need to be scheduled (the ones with the same delivery date). This would just be a place holder for a function to get information from later.
– Then from another rule (that calls a js function), refer to this rule and loop over the emails and get its to, bcc, cc, subject, body values.
– Then using custom js function add it to the custom list that is used to scheduling email. (This part I am already doing)I am just looking to see if we can avoid having to construct the emails from within javascript as supposed to having it setup using a rule which can greatly help with maintaining it down the road.
Hi Alex,
I see that a fix was provided for this issue in version 1.0.73. However, I feel like its only partially fixed. Here is the behavior I am seeing:
– Field1 is people picker field, Field2 is people picker field.
– Rule set field value (field1 is changed set the value in field2 from field1)
– When people are added to field1, they are getting added to field2
– When people are removed from field1, they are not removed from field2 (this feels like a bug)
– Only when everyone has been removed from field1, everyone gets removed from field2Right now I am getting around this by running two set field value actions in the rule.
– First set field2 to blank
– Then set field2 to field1 values.Thank you for all your work on this and I hope a fix will be issued in the next release, so the feature works in the most natural form than going through work arounds.
I dont know why there is a ’ at the end of the url, but the actual url is as follows:
https://xxxx.sharepoint.com/sites/Intranet/_api/web/siteUsers/getByEmail(‘%20xxxxx@xxxx’)Thank you for the work around and looking forward to an UI implementation to this in the future release.
I feel like we already got the new UI rolled out. That is when DFFS button wouldnt load for us unless we do a hard refresh. But after changing this setting, everything started to work. So its may be a YMMV.
For me things started working 90% of the time by changing the “Offline Client Availability” setting to “No” in SharePoint list “Advanced Settings”. Attached is a screenshot of the setting. Hope it helps others.
Attachments:
I have attached two screenshots where you can see i dont have the “Call Function” action or “Prepare Email” option after those actions have already been added to a rule.
I may have missed your reply about the other topic. I didnt see any updates in their. I will try to upload some screenshots to help explain the issue better.
