Forum Replies Created
-
Posts
-
Like many things, ‘It depends.’ It depends on the specific use case and requirements surrounding the email juxtaposed with the respective capabilities of DFFS email and SPD email workflows. When the requirements are fairly straightforward I am finding using the DFFS email HTML and inline CSS can be easier to develop, test, and deploy than SPD WF. However, if I need to set up more complicated scenarios (e.g., assign Tasks) then SPD WF may be appropriate.
An ongoing aggravation with SPD WF is the need to translate lookup fields and calculated fields into plain text and avoid null (blank) fields. Any of these cause the WF to be cancelled. The DFFS email accepts all of these fields without an issue. This is a big advantage and saves much development time.
I like being able to set a rule to display the DFFS email submit button for a single permission group and it’s invisible for everybody else.
Using DFFS email with the SPD WF option in DFFS is something I have not tried as seems a bit more complicated as you are merging the two systems.
Mike
The latter, i.e., I need to set values in List A based on values pulled back from List B.
Use case description:
Values in List B need to be copied to List A based on the field (multi-value) in common between the two lists. For example, the common Field 1 could have one or more values in List A. Find that set of matching values in List B and pull back to List A from List B:Field 2 (could have one or more values based on Field 1),
Field 3 (could have one or more values based on Field 1)This is similar to what SharePoint does with a multi-value lookup using Field 1 from List A to List B that also brings over multiple associated fields from List B to List A.
Mike
I use the top left buttons.
The URLs are different when initially accessing the Display form as shown here:
URL comparisons:
Directly accessing DFFS.aspx via this URL results in Display form missing fields (red bar warnings)https://[SITENAME]/dispform.aspx?GoToBackend=1&backend=1&targetList={7c8a9215-cff8-4176-b93d-1b9c656b6f91}&targetListBaseUrl=/sites/[SITENAME]&formId=/lists/[LISTNAME]/dispform.aspx&formType=1&saveLastGood=1&Source=https://[SITENAMEandLISTNAME]/dispform.aspx
The URL after accessing the DFFS backend from link at bottom of Display form (no missing fields or red warnings):
https://[SITENAME]/DispForm.aspx?ID=1270&backend=1&targetList={7c8a9215-cff8-4176-b93d-1b9c656b6f91}&targetListBaseUrl=/[SITENAME]&formId=/lists/[LISTNAME]/dispform.aspx&formType=2&saveLastGood=1&Source=https://[SITENAMEandLISTNAME]/DispForm.aspx?ID=1270
Should I use a different link to access DFFS.aspx directly?
Should I replace
/SPJS/DFFS/installer/Installer_CEWP_code.html
with
SPJS/DFFS/DFFS_DirectToBackend.html
in the DFFS.aspx page web part?Keith,
I’ve been developing a DFFS email capability and would be happy to share with you pros and cons vs. SPD WF emails that I’ve learned. Let me know.
Mike
Thanks! Works great. I knew it had to be something simple and just forgot to look at Alexander’s very helpful Tool Tip.
Keith,
I am interested in the JS code you mentioned above as I have several multi-line text fields in which multiple users enter text. Their self-submitted initials and date annotations are all over the board. Your JS would be helpful.Thanks
MikeBrett, not sure if you figured this out yet but Alexander posted a JS solution for this in 2015 that I’m going to use soon. Thought I’d pass on the link to you.
Display a calculated column display value in edit form?
Mike
Keith, I’m not the farm admin. I’ll query our admins to check on this and if it can be increased. Thanks for the tip.
Yes, using the link at the bottom of the Display form to access the DFFS backend does not result in the missing field issue.
Thanks Alexander. Now I can concentrate on the method that will work.
As a suggestion, it would be helpful if there was a transportable CSS file feature for DFFS emails. There is one for the entire form, but one just for emails would be helpful as it could then be easily applied across multiple lists. Perhaps a future version?
Mike
The items in List B are the same for all items in List A, i.e., every item in List A will always send DFFS-generated emails to the same recipients found in the one row List B.
No, I always use a bookmark to enter the DFFS backend directly:
/SPJS/DFFS/DFFS.aspx
and then I select the list form in which I want to work. Should I select the edit form before the display form? It seems I must reinitialize the edit form before the display form will once again list the display form only fields, i.e., calculated and associated lookup fields.
