[Alexander Bautz]

Hi,
Sorry for the delay. Currently it does not support anonymous access. I will try to add this to the next release, but this has been delayed due to work on DFFS.

Alexander

[Alexander Bautz]

I have updated the BETA of the frontend script to v2.104. You find the change log here: https://spjsblog.com/vlookup-for-sharepoint/vlookup-change-log/

Alexander

[Alexander Bautz]

Strange, I have not seen this before. Is it possible that you have some code that interferes with the date picker?

Alexander

[Alexander Bautz]

Hi, I have seen this happen if a user double clicks on the calendar icon. Does the calendar go away if you click the icon again?
Alexander

[Alexander Bautz]

Hi,
Thank you for the feedback – I will fix this error message in the production release of DFFS v4.210.

Alexander

[Alexander Bautz]

I’m glad it worked. I have not been able to recreate the creation of two identical configurations, but if two users at the same time starts configuring a form that does not have any current configuration, you can end up with duplicates.

If anyone have a “method” for creating duplicates, please let me know so I can prevent it.

Alexander

[Alexander Bautz]

This has been added to the latest BETA: https://files.spjsworks.com/?dir=files%2FvLookupForSharePoint%2FSP2010+and+SP2013%2FBETA%2F

Alexander

[Alexander Bautz]

I’m glad you figured it out.

Alexander

[Alexander Bautz]

Sorry, this is single choice only.

Alexander

[Alexander Bautz]

Hi,
I have confirmed this bug. It appears when you have duplicate entries for the current form in the configuration list.

I cannot tell exactly why you end up with duplicates, but I will add a check for it in the upcoming release so it will not affect the solution if you somehow manage to get duplicates.

If someone have a clue as to why you end up with duplicates, please let me know.

For now, you must manually remove the duplicate entry in the configuration list by going to /Lists/SPJSDynamicFormsForSharePoint/AllItems.aspx and deleting the oldest configuration for the affected form (look at the “Modified” date).

Alexander

[Alexander Bautz]

I’m glad you figured it out.
Alexander

[Alexander Bautz]

I’m not sure this is a good idea. The scripts will load for ALL pages, and not just the forms. This will make the page load slower as it has to query the DFFS config list to see if it finds any records.

You can try it, but it is not “officially” recommended.

Alexander

[Alexander Bautz]

Sorry, my bad – there was an error in the code example. See if this helps.

Alexander

[Alexander Bautz]

Hi,
This is no problem. Add this code to the header (see image attached):

PM Number: <span id="putPMNumberHere" />

Then use this code in the custom JS section in the Misc tab:

// For DispForm
$("#putPMNumberHere").html(getFieldValue("YourFieldName",true));
// For EditForm
$("#putPMNumberHere").html(getFieldValue("YourFieldName",false));

PS: “YourFieldName” is the FieldInternalName – change it for your actual field name.

Hope this helps
Alexander

• This reply was modified 10 years ago by Alexander Bautz. Reason: Fixed error in code example

Attachments:

1. 

   FieldValueInHeader.png
   

[Alexander Bautz]

I’m glad you figured it out!

Alexander

[Author]

Posts