Forum Replies Created
-
Posts
-
Ok, so I’m doing that but for some reason when it hits the autocomplete logic on the child form it doesn’t recognize the getFieldValue(“Field I’m Passing from Parent”); within the rest filter. I did a console.log and it shows “”, but after load it appears to show.
Maybe I need to wait for the form to load before passing?
Yeah I figured it was probably not worth the effort. Thanks for the input and info.
Apologies, I’m hoping this is my last question, and I may be overlooking/overthinking it but is there a way to pass field values on the parent form (edit form) to a new/edit child form? Reason being that I have a child list containing an autocomplete that needs to filter from the autogenerated ID of the parent.
One more question, if the main request form is in dialog, is there a way to redirect back to the main request view page, open the form in dialog and then incorporate some sort of alert to prevent the user from clicking cancel?
That may be too far fetched but the goal is to try and maintain as much of the workflow emailing within the main request form.
I think I figured it out but made it more complicated than it needed to be so I revert it to the remove child items on cancel for NewForm only.
I just need to wrap my head around the syntax for the document delete of the other vLookup.
I love this and this is exactly what I’m looking for. 2 questions:
If I’m keeping my edit/display form and new form JS logic together how can I create a global variable that let’s me know which form the current user opened (dialog or not)? That way I could set another variable to equal getFieldValue(“_vlookupID”) for New and spjs.dffs.data.thisItemID for Edit/Display?
If I have 2 vlookups – 1 child is a doc library the other is a list. Is it better to create one function/section to handle both break out into two different loops?
I managed to replicate the stretch issue on my personal SharePoint site due to the sensitive nature of my work’s site. I mocked up a similar layout and structure of the worksite using dummy data. Notice image 1 (in Edit Form) this is the normal layout. If I click the Request Tab again it stretches the form/headers (image 2). If I keep clicking it multiple times notice how the form/header continues to stretch (image 3).
I also tried to replicate the {author} issue I was having above the tab section however my personal site uses first last name format as opposed to Last, first name. In the users name I looked up, from work, they didn’t have any commas originally in their name except for what exists in the “Last Name, First Name” format used.
Let me know if you need anymore info and/or have any questions.
Attachments:
Quick update – had a team member test for me…
It still occurs when there is one auto populates read-only text field on the same SBS index or SBS index below the autocomplete field but it does not happen when text field is not put in any SBS index.I’m away from my computer this week, but I found what’s triggering it. I have an auto complete field (single value) that populates 4 additional text fields. Removing all 5 fields or collapsing the section stops it from stretching. When I add the autocomplete field back it’s also fine. If I add back 2 or more of the text fields that auto populate from the autocomplete choice the stretch problem returns.
The {author} issue with the “,,” is in HTML I added above the tabs similar to the following:
<div class=“tableDiv”> <table class=“tableDetails”> <tr> <td><span class=“styleFont”>Created By: </span>{author}</td> </tr> </table> </div>Hopefully that helps and I can try and send some screenshots when I get back.
It’s version DFFS v4.4.5.24.
I’m only seeing it occur on one tab and it’s also the only tab with auto-complete fields (2 in total). The auto-complete fields are not wrapped in a document ready function.
Oh I’m also noticing too that {author} usage puts 2 commas in the name such as Smith,, John. I used JS replace to fix it on load.
It’s version DFFS v4.4.5.24.
I’m only seeing it occur on one tab and it’s also the only tab with auto-complete fields (2 in total). The auto-complete fields are not wrapped in a document ready function.
Got it that’s right, the Misc Tab. Speaking of that I thought there was an option to hide detail/descriptor info on fields? I ended up hiding them in css so no issues there.
That makes sense with the css elements in your example. I overlooked the anchor tag and thought the current tab styling was being done at just the tabBase class level. I’m still re-learning css after years of not using it.
I greatly appreciate it, thank you for all the help!
2 more questions if you don’t mind me asking:
Is there a way to include html above the tabs or should I use the script/content editor webpart for it?
Tab css customizations can be done in the Tab Name section but if I wanted to do it in custom css do I reference the tabBase class?
I had a feeling so I modified it exactly as you mentioned and went with the side by side approach. Also thank you so much for the styling, that is super clean compared to my “hack-n-slash.”
Apologies I didn’t submit image
Attachments:
