[Alexander Bautz]

Sorry for the delay. This is not possible without custom making a dialog. In the example you have an ok or cancel button, and you can use them to set a field value for OK and another for Cancel. Here is an example on how to set the value:

setFieldValue("FieldNameHere","value you want to set");

Hope this helps,
Alexander

[Alexander Bautz]

You can send some screenshots by email. You find my email in the “About me” tab.
Alexander

[Alexander Bautz]

Ensure you have put the license code above the DFFS_backend.min.js in the “DFFS_backend_CEWP.js.aspx”, and above the DFFS_frontend_min.js in the file “DFFS_frontend_CEWP.js.aspx”.

Refer the installation manual section 2.3.3. and 2.3.4: https://files.spjsworks.com/files/DynamicFormsForSharePoint/v4/InstallationManual/How%20to%20set%20up%20DFFS%20v4.pdf

Let me know if this helps,
Alexander

[Alexander Bautz]

Hi,
Sorry for the late reply. Somehow the email regarding this post ended up in my spam folder. It seems I have a bug with the “list name detection” in the vLookup script as the proper CAML query parameter should be “Issue%20and%20Process%20Escalation:vLooup” and not “sites:vLookup”.

I’ll look into it and post a fix.

PS: When creating vLookup columns, you only have to prefix it with vLookup. Your field names can be like this:
vLookup_issues
vLookup_tasks
and so on…

Alexander

[Alexander Bautz]

Hi,
I have not seed this before, can you post a screenshot of the error message?

Could there be some items with item level security, or items with that have lookup columns into other lists that the person does not have access to?

Alexander

[Alexander Bautz]

I’m glad you figured it out – I had no knowledge of this setting!

Alexander

[Alexander Bautz]

Hi,
Have you tested without DFFS to verify if it is actually DFFS that causes this login prompt?

You can try using the “Network” debugger in the developer tools (hit F12) to see what is requested when the login prompt occurs.

Alexander

[Alexander Bautz]

Hi,
Finally published v2.003 of the frontend vLookup script. This fixes the bug with space in the list name (in the URL). You find the link to the updated file under “Download and install” here: https://spjsblog.com/vlookup-for-sharepoint/

Alexander

[Alexander Bautz]

Hi,
It looks like the scripts are wrapped in

<!-- a comment tag -->

The comment tag is there in the example code, but you must move the vLookup script out of this comment tag to “activate” it when you have fixed the src.

Alexander

[Alexander Bautz]

Hi,
Sorry, but this is not possible without using javascript to hide the lines. This is because the vLookup childres are not stored on the parent list item – they are retrieved on the fly when you load the list view.

Alexander

[Alexander Bautz]

Thank you for the feedback – and for the “beer”. I’ll publish an “official” update later tonight.

Best regards,
Alexander

[Alexander Bautz]

Hi,
It is the space in the list name that causes this problem. Can you verify that this patched version works: https://files.spjsworks.com/files/vLookupForSharePoint/SP2010%20and%20SP2013/DEBUG/vLookup_frontend_BETA.js

If it does, I’ll update the official release with the fix.

Thank you all for the feedback,
Alexander

[Alexander Bautz]

I have rigged a new DEBUG version of vLookup frontend. Get it here: https://files.spjsworks.com/?dir=files%2FvLookupForSharePoint%2FSP2010+and+SP2013%2FDEBUG%2F

Post the output in a new comment in this topic.

Alexander

[Alexander Bautz]

Sorry for the delay – still the same error means that it complain about the “Title” field still? – or is it now complaining about the new field?

Alexander

[Alexander Bautz]

Sorry, but the autocomplete does not trigger when you set the value by a rule in DFFS.

You should be able to do this using “Set field value” in a DFFS rule using this in the “Value” field:

{currentUser:Name}

How is it you are filling the fields when you must hit the validate button?

Alexander

[Author]

Posts