[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

[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

[Author]

Posts