Search Results for 'list form'

[Paul Lynch]

Hi Alexander,

I am not a fan of using Content Types when DFFS can effectively replace their necessity. But I have an old list that I am trying to implement it on that needs to keep their three content types.

The issue I have is that I want to use the Query URL parameter to create a new form, but also to set the content type at the same time.

Idea 1 – Somehow incorporate the Query URL parameter into the button url, so that it also sets content type?

Here is my custom link to add an item to the list:
https://xxx.sharepoint.com/teams/site/Lists/NAMEOFLIST/NewForm.aspx?Source=https://xxx.sharepoint.com/teams/site/Lists/NAMEOFLIST/View.aspx?PageView=Personal&ShowWebPart=%7B5B894272%2D5831%2D4A0B%2DB8C2%2D3184C94650DE%7D&ContentTypeId=0x010003D8415BFE122145BE9C8717F2580443003FAB0C9E7156E94DA988BEF82E06218E&RootFolder=/teams/site/Lists/NAMEOFLIST

Idea 2 – After the normal “Item” content type is created, when user sets a field, it sets the content type.

Sets Field=A – rule or JS does nothing
Sets Field=B – rule or JS sets Content Type B
Sets Field=C – rule or JS sets Content Type C

I’ve been trying to do this without success in the NewForm or EditForm using a rule (which I debug checked is running) but nothing changes in form (I have content type field visible in edit form).

 {inline}
 setFieldValue("ContentTypeId", "0x010003D8415BFE122145BE9C8717F2580443003FAB0C9E7156E94DA988BEF82E06218E");
  setFieldValue("ContentType", "Type B");

Kind Regards,
Paul

[Alexander Bautz]

This is very strange. I have tested a similar setup and cannot reproduce it. Could you send me some screenshots of your custom js, your form where you have the autocomplete and the list where you have the data to fill the autocomplete field and I’ll try to figure out what is going on.

Send it to the email you receive the forum notifications from.

Alexander

[MikeS]

This file is loaded before executing the Autocomplete Custom JS

_scripts/PullInformationFromConnectedList.js

Complete AC code:

spjs.ac.textField({
 "applyTo": "TemplateType",
 "helpText": "",
 "loadText": "",
 "listGuid": "{redacted}",
 "listBaseUrl": "redacted",
 "showField": "Title",
 "searchFields": ["Title"],
 "filterCAML": "",
 "useREST": false,
 "preloadData":false,
 "filterREST": "",
 "optionDetailFields": [],
 "optionDetailPrefix": [],
 "enforceUniqueValues": false,
 "rowLimit": 30,
 "listOptionsOnFocus": true,
 "minLengthBeforeSearch": 1,
 "reValidateOnLoad": false,
 "allowAddNew": false,
 "isLookupInSelf": false,
 "addNewAdditionalFields": [],
 "multiselect": false,
 "multiselectSeparator": "; ",
 "orderBy": [
    {
 "fin":"Title",
 "ascending":true
}
     ],
 "clearSetFieldsOnInvalidSelection": true,
 
 // the setFields section of your AC function call:
 "setFields": [
     {
			"fromFIN":"Fin1",
			"joinBy": "",
			"toFIN":"Fin1",
		    "parseFunction": "customParseFn",
            "skipIfEmpty": false
		},
		{
			"fromFIN":"Fin2",
			"joinBy": "",
			"toFIN":"Fin2",
			"parseFunction": "customParseFn",
            "skipIfEmpty": false
		},
	    {
			"fromFIN":"Fin3",
			"joinBy": "",
			"toFIN":"Fin3",
			"parseFunction": "customParseFn",
            "skipIfEmpty": false
		},
		{
			"fromFIN":"Fin4",
			"joinBy": "",
			"toFIN":"Fin4",
			"parseFunction": "customParseFn",
            "skipIfEmpty": false
		},
		     {
			"fromFIN":"Fin5",
			"joinBy": "",
			"toFIN":"Fin5",
		    "parseFunction": "customParseFn",
            "skipIfEmpty": false
		},
		{
			"fromFIN":"Fin6",
			"joinBy": "",
			"toFIN":"Fin6",
			"parseFunction": "customParseFn",
            "skipIfEmpty": false
		},
	    {
			"fromFIN":"Fin7",
			"joinBy": "",
			"toFIN":"Fin7",
			"parseFunction": "customParseFn",
            "skipIfEmpty": false
		},
		{
			"fromFIN":"Fin8",
			"joinBy": "",
			"toFIN":"Fin8",
			"parseFunction": "customParseFn",
            "skipIfEmpty": false
		},
				{
			"fromFIN":"Fin9",
			"joinBy": "",
			"toFIN":"Fin9",
			"parseFunction": "customParseFn",
            "skipIfEmpty": false
		},
	    {
			"fromFIN":"Fin10",
			"joinBy": "",
			"toFIN":"Fin10",
			"parseFunction": "customParseFn",
            "skipIfEmpty": false
		},
		{
			"fromFIN":"Fin11",
			"joinBy": "",
			"toFIN":"Fin11",
			"parseFunction": "customParseFn",
            "skipIfEmpty": false
		},
	],
 "debug": false
}); 

• This reply was modified 4 years, 1 month ago by MikeS.

[Paul Heffner]

I added a new folder under SPJS for the new version, I am now using the new installer. I uninstalled DFFS on all 3 forms for both lists and reinstalled from loader 2.

I didnt have to update any settings and all the options look correct but still no parent/child showing up in the form.

Looks completly normal and still works so that is a plus

[MikeS]

Alexander,

I’ve tried this on New and Edit forms and it is not working as needed. If there are blank fields in the source list record the Template Type is not showing up in my Autocomplete Template selection field. Kind of opposite from what I need. In order to better communicate what is needed I’ve attached a diagram that should help.

Thanks
MikeS

Attachments:

1. 

   DFFS_Autocomplete_diagram.png
   

[Bryan Waldrop]

I know that setting the _vLookupID /DFFSID is set by submitting a new item or editing and exiting item through a DFFS form.

I have a unique situation where my partners want to submit a large number of historical items via datasheet view in the parent list.

Rather than having to edit and save each item to create those IDs, is there a script that can be placed on the datasheet view page that will execute a DFFS function and create _vLookupID /DFFSID ?

[Alexander Bautz]

If you give each of the buttons an ID and hide them initially:

<input type="button" id="archive_btn" style="display:none;" value="Archive" onclick="the_archive_function()">
<input type="button" id="undo_archive_btn" style="display:none;" value="Undo archive" onclick="the_undo_archive_function()">

You can now set up two rules – one for “Archived = yes” and one for “Archived = no” – have them run ON FORM LOAD only and add the ID of the button you want to show in the “Visible headings or elements” textarea. This will now show the correct button based on the archived field being checked or unchecked.

Regarding the visibility in list view: you must ensure that the code actually sets the “Archived” field to false when you run the function and that the view is actually filtered on that field.

Alexander

[BenR]

Alexander,

I hope you are well.

I have an issue with one list configuration which seems to expose a difference in Rule processing between DFFS_v4.4.5.18 and DFFS_v4.4.5.19 – and carries on to DFFS_v4.4.5.20.

● The primary symptom is that when opening a form, NewForm, EditForm, or DispForm, will not complete rendering, resulting in the “This took forever!” error message. I have narrowed down this symptom to three linked rules.
● A secondary symptom is that disabling the three linked rules identified above does not remove the symptom, however deleting the three rules does.

Notes:
The unaltered configuration tested with the following versions:
● DFFS_v4.4.5.20 – FAIL
● DFFS_v4.4.5.19 – FAIL
● DFFS_v4.4.5.18 – SUCCESS
● DFFS_v4.4.5.17 – SUCCESS
● DFFS_v4.4.5.16 – SUCCESS
In this configuration, NewForm was created first, and copied to EditForm and DispForm.

The three rules (Nos. 2, 3, & 4) are linked:
● No. 3 to 2
● No. 4 to 2 and 3

Each rule sets one Required field, and nothing else. Please see the attached images to illustrate the settings:
● Rule No. 2
● Rule No. 3
● Rule No. 4

Please tell me what I can do to releave this error or to troubleshoot further.

As always, your support and efforts are greatly appreciated!

R’grds – Ben.
Reference:

Successful version:
Version information
Custom DFFS-folder: DFFS_v4.4.5.18_2021-03-05
DFFS Loader: v2
DFFS frontend: 4.4.5.18 – March 05, 2021
DFFS frontend CSS: 4.64 /
Autocomplete: 1.6.51 – February 07, 2021
Cascading dropdowns: 3.7.44 – February 07, 2021
jQuery: 1.12.4
Lookup: 1.1.20 – March 10, 2020
Resource management: 2.4.5 – August 29, 2019
SPJS-Utility: 1.350 – February 21, 2021
vLookup: 2.2.160 – February 21, 2021

FAILING version:
Version information
Custom DFFS-folder: DFFS_v4.4.5.20_2021-03-21
DFFS Loader: v2
DFFS frontend: 4.4.5.20 – March 21, 2021
DFFS frontend CSS: 4.64 /
Autocomplete: 1.6.51 – February 07, 2021
Cascading dropdowns: 3.7.46 – March 21, 2021
jQuery: 1.12.4
Lookup: 1.1.20 – March 10, 2020
Resource management: 2.4.5 – August 29, 2019
SPJS-Utility: 1.350 – February 21, 2021
vLookup: 2.2.161 – March 21, 2021

Attachments:

1. 

   Rule-No.-2.png
   

2. 

   Rule-No.-3.png
   

3. 

   Rule-No.-4.png
   

[Todd Fleming]

I have link from each item in one SharePoint list to add the item to the second list. The link from the first list is a calculated field with query string at the end that opens a new item form on the second list. The link ends with /NewForm.aspx?ID=6&Source=http://…

I would like for the ID number to be saved in the new list in a field called CatalogID, the form to automatically be saved and the user directed to the URL specified in the source value in the URL. This all works with a manual save, but when I add a trigger save function into custom JS, the record saves, but without the value in the CatalogID field. Any thoughts on how to achieve the behavior and allow the URL to be read and value saved? The entire code for custom JS that I am using is:

var fields = init_fields_v2();
var yourQueryStringVal = GetUrlKeyValue(“ID”);
setFieldValue(“CatalogID”,yourQueryStringVal);

spjs.dffs.triggerSave();

[Keith Hudson]

Andra, you said you deleted your “new item form in error”. Do you mean that you deleted the NewForm.aspx on your list accidentally? That is a SharePoint issue, and you would need to restore or recreate your NewForm.aspx on the list before using DFFS on that form.

[Alexander Bautz]

You can click the “Enhanced with DFFS” link to enter setup and then click the Export, import and restore tab > Brower restore points and deleted configurations.

Not sure why you get the error message in the DFFS installer, but ensure you are actually loading the correct installer (the correct URL) – if you have mulitiple DFFS installations (on the root site and in a subsite for example) your form might have been installed with another DFFS installer.

If this is the case, go to your primary DFFS installer and uninstall / reinstall DFFS in this form / list.

Alexander

[Andra Mitchell]

I deleted my new item form in error. Is there anyway to retrieve the new item form? When I attempt to access the NewForm via configurations, a popup message displays: DFFS Installer – run initial setup. This is the first time you access the DFFS installer, or you have updated DFFS to a new version. Click the button to complete the setup. I have other DFFS list that open in the backend without receiving that message.

[Keith Hudson]

SharePoint will do the heavy lifting easily for you using calculated columns. However, since calculated columns are not calculated until you save the item, and since they are not in the field dropdown picker on a DFFS form (if I’m wrong on either of those two points, someone please correct me) one possible solution is to NOT use DFFS.

You could build a simple SharePoint list with a single date field (make sure the Title field is not required), build a calculated date field for each due by date, and build a Datasheet (aka Quick Edit) view of the list where the user simply enters their Deploy Date, then clicks on the empty line below, and the calculated dates will all appear as soon as the record is saved.

In order to not clutter the list (since the records do not need to be saved long term) you could build a SharePoint Designer workflow that starts as soon as an item is created, pauses for 10 minutes (or 10 hours or 10 days – whatever interval you want) and then deletes the item from the list.

In order that the view is always blank when someone comes to it, filter the view to only show items where Created is equal to [today] + 1.

That approach may not meet your needs, but I thought I would suggest it as a possible simple solution in case it DOES meet your needs.

DFFS is amazing, but even native SharePoint can do ‘magical’ things when we apply a little creativity.

(Side note: if this turns out to be the exact solution you need, don’t fault yourself for not thinking of it earlier. I too spent several hours trying to develop a tool once using DFFS, and finally realized that a simple Quick Edit view would do everything I needed simply and elegantly.)

Good luck!!

[Alexander Bautz]

Hi,
To fix a breaking change that Microsoft introduced late last year I had to change the DFFS installer to write the default NewForm, DisplayForm and EditForm URL to the list schema. This means that changing the URL of a list requires that you use the DFFS installer v2.0.1.0 or later to uninstall and then reinstall DFFS to this list.

In addition to this uninstall and reinstall you must go to the list /Lists/SPJSDynamicFormsForSharePoint to find your configs for NewForm, DispForm and EditForm and change the Title to match the new list URL.

Alexander

[Halim Lahoud]

Hello,
I had DFFS installed and configured on a SharePoint site but we had to change the URL of the site.
after changing the URL I am getting errors on the DFFS forms.
any solution on how I can fix this problem without loosing the configuration done on the lists

thank you in advance