Home › Forums › Modern DFFS › vLookup Document upload form
- This topic has 13 replies, 2 voices, and was last updated 8 months ago by Alexander Bautz.
-
AuthorPosts
-
-
January 31, 2024 at 20:42 #37440
Hi Alex,
when using the vLookup function in combination with Documents when uploading a document in the classic dffs a form popped up to enter details for the document.
this is not happening in the modern DFFS or am I missing a checkbox? When the document is uploaded and the edit pencil is pressed the form comes up to edit details.
thanks.
Christoph -
January 31, 2024 at 23:52 #37441
This is not an option in the current version, but I’ll look at adding that functionality in a future version.
Alexander
-
February 1, 2024 at 09:41 #37442
this would be not only a great addition but in my oppinion a must feature ;-).
Any guess for the time of implementation?
Same would apply for list items (if this is not already the case – not used yet)
thanks.
-
February 1, 2024 at 16:21 #37447
I’m planning a new version hopefully over the weekend, but I’m not sure if I’ll be ale to get this one in that release – I’ll see what I can manage. If not, it should be fixed in a week or two.
Lists already work as the form is the primary input so you fill in the form and save.
Alexander
-
February 6, 2024 at 16:27 #37464
Hi,
I added this new functionality in the new version – can you test it and let me know how it works?Alexander
-
February 6, 2024 at 20:01 #37465
Hi Alex,
adding documents and opening the edit screen works like a charm but maybe it is me not doing the setup correct but it seems the prefill of values does not work correctly.
screenshot attached of the setup but it does not prefill the fields.
best.
ChristophAttachments:
-
February 6, 2024 at 20:13 #37467
ok, it was my bad… everything works like a charm.
regarding the lookupvalue… in the classic dffs there has been the values vLookupID and vLookupParentID to match entries. For the modern DFFS is this to be done manually by matching and fill fields?
best
-
February 6, 2024 at 20:30 #37468
I’m glad it worked – I just tested and could not reproduce it…
Regarding the ID, you can still use _vLookupID and _vLookupParentID if you like – if you add the _vLookupID column to your list, it will auto-populate like it did before.
You can also use a column named “_DFFSID” – add it to your list and use the automatically generated ID to transfer to a field you can call _DFFS_ParentID (or whatever you like) and use the same logic as for _vLookupID and _vLookupParentID.
I just realized that I had not documented this in the user manual – I’ll add it.
Alexander
-
February 7, 2024 at 21:10 #37481
Hi Alex,
so I tried the setup with the _vLookupID and _vLookupParentID as I used to do with the classic DFFS.
The Filter in the vLookup in the Parent List is _vLookupParentID eq [[fieldValue:_vLookupID]]
but when trying on the frontend it says the syntax is not valid.
Attachments:
-
February 7, 2024 at 21:18 #37483
The filter value must be in single quotes like this:
_vLookupParentID eq '[[fieldValue:_vLookupID]]'
Alexander
-
February 7, 2024 at 21:27 #37484
now I get the error the column does not exist.
sorry to bother you.
Attachments:
-
February 7, 2024 at 21:29 #37487
No problem – I forgot a little quirk when using a field that starts with an underscore in a rest filter – you must prefix the field name with OData_ like this:
OData__vLookupParentID eq '[[fieldValue:_vLookupID]]'
Alexander
-
February 7, 2024 at 21:36 #37488
last for tonight.
so far so good. when using the prefill function for the IDs I get an error when uploading a file.
it says
The property XX is not existing for type YY. make sure to use only defined property names.
Attachments:
-
February 7, 2024 at 21:57 #37490
It might be a similar issue related to using an underscore – try changing the name of the _vLookupParentID field to not start with an underscore (you must delete it and recreate it without the underscore) and see if that helps.
Alexander
-
-
AuthorPosts
- You must be logged in to reply to this topic.