[Paul Lynch]

Unfortunately ‘Select this tab’ does not make a difference.

I think because it does select the first tab correctly.

I just cannot work out why some fields will show and others will not. Tried many things like adding and removing the fields, creating a new field etc..

Once you actually click on the first tab (even though it is already appears selected on load) – the rest of the misisng fields suddenly appear!

hopefully the next release fixes this thanks!

[Paul Lynch]

Thanks Alex, the SBS setting to span both columns was spot on!

[Paul Lynch]

I think I might have found a clue to the issue.

In the Parent library 1 – the vlookupTHISISID column is blank.
In the Child library 2 – the vLookupParentID column is also blank.

In other working vlookup lists these should have a format like this 28:1487311669532 with the first number being the ID.

I’m not sure why this is not populating though!

Attachments:

1. 

   brokenvlookup.png
   

[Paul Lynch]

additional screenshots added here..

Attachments:

1. 

   dffs1.png
   

2. 

   dffs2.png
   

[Paul Lynch]

Although I have no issue now, perhaps I could ask a question on functionality.

Right now it is working great, I can click the + button to do a vlookup and it will create a new item in the child list and show it in the table on my parent form.

But what is I wanted to both add new child items, or select from existing ones?
Would this possible?

I guess all the code has to do is set the value in the child vLookupParentID column.

This lookup would be overwritten if two parents tried to associate with a single child. So only one distinct child item could be associated with one parent item, or perhaps if the vLookupParentID accepted multiple values, it could then associate with different parent items?

[Paul Lynch]

The error itself did not make sense as the Child List (and Child item has a vLookupParentID field (same internal field name).

Although I just noticed that this field was set to Hidden in the Child list Item Content Type, I just set it to optional and it is now fixed and not appearing in the form.

Strange sorry FIXED!

[Paul Lynch]

Sorry Alex, for some reason I missed this page that explains it all very clearly. Please ignore this!

https://spjsblog.com/vlookup-for-sharepoint/vlookup-setup-example-for-sp-2010-and-2013/

[Paul Lynch]

I guess put more simply.

Can you join any two custom lists together?
Or do you need to create a parent and child list?
Do you need to be able to write scripts to make this solution work? (or at least create the parent and child lists).

[Paul Lynch]

Thanks Alex, all working now, that was dumb!

[Paul Lynch]

Note I did not manage to capture the screen shot of the drop down, I was too slow 🙂

[Author]

Posts