[Alexander Bautz]

Add this code to the Custom JS section:

function dffs_PreSaveAction(){
	if(!confirm("Save the form?")){
		return false;
	}
}

Alexander

[Alexander Bautz]

Hi,
I had completely forgotten that I had rigged some basic debug alerts in the vLookup frontend – try adding this to the URL:

.../AllItems.aspx?vLookupDebug=1

This should produce three alerts for each vLookup column in the view (blob, query and itemcount).

Let me know if someone of you can test this, and If you get NO alerts I’ll rig a new debug version that does it more thoroughly.

Thanks for the patience,
Alexander

[Alexander Bautz]

Hi,
I suspect you have the wrong URL to one or more of the files required for the backend, or that you have hidden the CEWP in the web part configuration.

Do you get any errors in the developer console (hit F12 > Console)?

Also, you should update to the latest version (currently v4.200).

Alexander

[Alexander Bautz]

Hi,
I’m struggling to recreate this. Is it possible for me to access a site where I can see this problem “live”?

If some of you can give me access, please email me – you find my email in the “About me” tab in the top of this page.

Alexander

[Alexander Bautz]

OK, I have a suspicion as to what the cause could be. Can you help me verify it by adding this code to the CEWP that you use in the list view:

<script type="text/javascript">
setTimeout(function(){
	spjs.vLookup.init();
},1000);
</script>

You should add it just below this line:

<script type="text/javascript" src="/[your path to the file]/vLookup_frontend_min.js"></script>

This will initiate the vLookup script “manually” after 1000 milliseconds.

Let me know if this works and I’ll look into a fix.

Alexander

[Alexander Bautz]

Hi,
I cannot recreate this error, can you confirm that the list view actually works with v1.7x of vLookup?

Alexander

[Alexander Bautz]

Your setup looks OK. Can you try using another single line of text field than the Title field?

If you are using SP 2013 you might have to delay the function call by wrapping it like this:

setTimeout(function(){
// add function call here
},500);

Alexander

[Alexander Bautz]

Hi,
Sorry, but this error does not sound like it originates from vLookup. It may cause vLookup to not function, but I cannot see that it is the source of the error.

Anything else that might give me a clue as to what could be wrong?

Alexander

[Alexander Bautz]

There are no issues thet I’m aware of. Do you get any errors in the developer console (hit F12 > Console)?

Alexander

[Alexander Bautz]

Not that I know of, sorry.

Alexander

[Alexander Bautz]

I have not tested it with document sets (and I have no experience with document sets either). Do you have the solution set up and working in another list or library to ensure you have the setup correctly?

Alexander

[Alexander Bautz]

I’ll look at this in the next release. The orphans tab is intended used when setting up the solution to let the person building the form know what columns that is not used. I recommend turning this off for “production”.

Alexander

[Alexander Bautz]

Sorry for the delay, do you get any errors in the developer console (hit F12 > Console)?

Alexander

[Alexander Bautz]

The save item bug was fixed in BETA 1 – now BETA 2 is the most recent: https://spjsblog.com/dffs/dffs-change-log/

Alexander

[Alexander Bautz]

You will need a third party plugin like bullzip (free) to “print” to a PDF-file on your computer. If you want to use a workflow, you can look at for example muhimbi (starting at $1499)

Alexander

[Author]

Posts