[Alexander Bautz]

Hi,
I have confirmed a bug where “[[item:link_disp]]” and “[[item:link_edit]]” fails to pick up the ID of the item from NewForm and also fails to get the correct PageType. I’ll get it fixed and publish a new version tomorrow.

You can construct the link manually like this – I think it should work in the current version also:

https://contoso.sharepoint.com/sites/your_site/_layouts/15/SPListForm.aspx?PageType=4&List=your_list_guid&ID=[[fieldValue:ID]]

Alexander

[Alexander Bautz]

This should be fixed by adding min-width in the new version v1.1.5.0.

Alexander

[Alexander Bautz]

I think I found what caused the bug, but cannot tell exactly why it suddenly started to fail after 15 years – it must be a browser issue I guess.

Let me know if the new version (DFFS v4.4.5.54 / vLookup v2.2.167) makes any difference.

Alexander

[Alexander Bautz]

OK, one option is to manually add the Content Editor Web Parts that loads DFFS to the forms (NewForm, DispForm and EditForm). Just open the form and edit the page and insert a CEWP above and one below and refer a working list to copy the Content Link URL. Set both the webparts as Hidden.

This will “install” DFFS without using the DFFS Installer.

Alexander

[Alexander Bautz]

Did you try my suggested solution (installing DFFS in the subsite and installing it from there)?

Alexander

[Alexander Bautz]

Can you email me the external js-file (or at least an example of a function) so that I can see the relationship between the custom js function and the one loaded in the external file?

I tried going back to v1.0.50.0, but still could not get a function in Custom JS marked as async to load from a rule, or from a call from an external file.

Alexander

[Alexander Bautz]

Hi,
I have tested and I’m not able to call a function marked as async from a rule in v1.0.83.0 either.

I’m not sure why you would mark the function as async in the first place – can you explain what you are trying to do?

I tested calling a synchronous function that again calls an asynchronous function and it works as expected.

I tested using this custom js:

async function asyncFn(){
  console.log("Running async function...");
  return "This is a message from the async function...";
}

function syncFn(){
  console.log("Running sync function...");
  asyncFn().then(message => {
    console.log(message);
  });
}

I called the “sync” function from a rule and this is the console output:

21:56:01.431 VM92546:25 Running sync function...
21:56:01.431 VM92546:20 Running async function...
21:56:01.435 VM92546:27 this is a message from the async function...

Alexander

[Alexander Bautz]

You must turn it on in the Miscellaneous tab in the DispForm configuration – see screenshots.

Alexander

Attachments:

1. 

   Version_history_restore_version_1.png
   

2. 

   Version_history_restore_version_2.png
   

[Alexander Bautz]

I deleted the one I had in my app catalog and downloaded the latest one from here:

It shows as 1.1.4.0 – see attached image.

Can you try deleting it from the app catalog and then empty the recycle bin and add it again?

Alexander

Attachments:

1. 

   v1.1.4.0.png
   

[Alexander Bautz]

Hi,
I have released a new version that I think should fix the web selector issue in vLookup. Check out the change log here: https://spjsworks.com/changelog/

Alexander

[Alexander Bautz]

Can you email me some more details / screenshots so I’m sure I fully understand what you mean?

Alexander

[Alexander Bautz]

Hi,
I’ll add this info as a third parameter (boolean) to the function in the next version – so you can use it like this from v1.1.4.0:

function dffs_PreSaveAction(exit, autosave, goToEditForm){
  // Your own code here
}

I hope to get the new version out later this week.

Alexander

[Alexander Bautz]

I’m sorry, but I don’t have any method for doing that. The vLookup code uses the default upload control and it is not possible to inject any code there to change the document name.

It is possible to add the documents to folders that can have unique names – for example pulled from a field in the current item. See the vLookup config “Add new items to this folder” field.

Alexander

[Alexander Bautz]

My initial approach of using a List view command set extension to override the default form proved to be a bit unreliable and I had no choice but to change it to the officially approved method using a Form customizer extension. The slower loading is unfortunately a side effect of using the official method as it is opening the page /_layouts/15/SPListForm.aspx and renders the form there.

I’m continuously looking for ways to improve DFFS, but until Microsoft offers another way to open a custom form in for example a side-panel I cannot really doo anything about it.

The link format you used should still work, but for new links you can either use this format:

.../Sites/YourSite/Lists/YourList/DispForm.aspx?ID=123

Alternatively you can use the format used by SharePoint on this format:

.../Sites/YourSite/_layouts/15/SPListForm.aspx?PageType=4&List=[GUID OF YOUR LIST]&ID=[ITEM ID]

PageType 4 = DispForm, PageType 6 = EditForm and PageType 8 = NewForm

Restoring a previous version requires that you check the “Show link to open the default version history page to enable restoring previous versions” button in the Misc tab – it gives you a link to the Standard SharePoint version log (it’s not possible to restore a version using custom code).

Alexander

[Alexander Bautz]

Hi,

I’m not able to recreate this issue. Can you email me some screenshots of the URL when you get this error message so I can try to recreate it?

Also include the browser you are using.

Alexander

[Author]

Posts