Forum Replies Created
February 23, 2016 at 21:10 in reply to: Suggestion: Download button, file icon and mouse-over view for images #10415
Thank you for this code! I am able to use the “FileLeafRef” in the ViewFields, and I do see a link to the file in the vLookup on the form, but the code does not change. I see you ask that the iArr be updated, but there could be any of those file types, so I would not want to limit what shows.February 23, 2016 at 17:39 in reply to: Delete "button" on child item with refresh for document library #10411
No errors, just what I included in the screen shots above.February 22, 2016 at 23:26 in reply to: Load parent form with folders in "open" state on load #10394
Thank you! This works perfectly!February 22, 2016 at 15:35 in reply to: Delete "button" on child item with refresh for document library #10371
I am using 2.252 of vLookup. I did try ID and it did not fail, but it just showed the ID number and there was no link.February 19, 2016 at 20:47 in reply to: Load parent form with folders in "open" state on load #10352
Is there any way to have the mouse-over state of the folder always on, so the upload button always shows? Is there a way to change the upload button image to text or a different image?February 19, 2016 at 17:17 in reply to: Delete "button" on child item with refresh for document library #10348
I apologize if I am missing something simple, but when I follow these instructions, I get the error I attached. Did I setup the ViewField correctly? Maybe I need to create an actual field?
Attachments:February 19, 2016 at 16:56 in reply to: Load parent form with folders in "open" state on load #10346
Thank you for this code! It works perfectly!
I wanted to add a new screen shot, the error is still happening in vLookup v2.260. My instructions above as to what happens still apply. The data comes over correctly from the parent edit form to the child new form, but when I click Save on the child new form, I get the attached error. It does let me save, just throws this error.
Thank you for fixing this, it works perfectly now! I am using v2.260 of vLookup.
The parent is NewForm.
I am using 2.258 frontend and 2.254 backend. Should I go back to the versions you listed?
I will try to record it, but here are the steps:
1. I have created the vLookup to pass data from a single-select lookup field in the parent to the child (content types are used, so it is actually the exact same field in parent and child).
2. When I go into the parent edit form and click the “plus” to create a new child, the data in the parent field is correctly sent and is visible in the child field.
3. When I save the child form, the error comes up, but the data in the field is still visible in the child field.
4. When I save again, the form allows me to save the field.
If I were to refresh the child form without saving it, then the child field no longer has the data, so even thought the data is passed from parent to child, and is correctly selected in child, somehow DFFS does not see it being selected in the child form.
It does bring the data over to the child from the parent correctly (shows the correct field selection), and on save it maintains the same selection. When I do a refresh of the form, it disappears. When I click save again, it saves it with the correct selection.
I updated to the latest vLookup versions as well, still getting the same error.
I just updated the SPJS utility file to 1.258; I still get the error.