Forum Replies Created
-
AuthorPosts
-
Unchecking Hide did the trick, and it would let me change it to another year.
When the field was still hidden, I had tested it and it did pass the year to the child list.
I’ve really never used vLookup before, so this is all new to me. I had inherited this site from someone else and the former developer used a lot of features I had not used before. So it’s a good thing. And the forums have been very helpful!Better new form with prefill. Didn’t notice I reversed the image.
Attachments:
Screen shots of the new form. One example with out the prefill, the other with the prefill.
Attachments:
Here is the vLookup configuration screen shots.
vLookup-3 shows no prefill. This is how I currently have it set so users can create the new form.Attachments:
The field was changed from a plain text to a rich text. The records that were showing html code were entered before the field was changed (this is a site that was recently given to me). Records added later are working. I just had to reenter the ‘bad’ records to get the html to work.
Thanks!!That did it!
There was one file on the new version that wasn’t on the old version, ext-themelist.js. Do I need to do anything with it or just leave it there?Thanks for all your help!!
CarlIt did not like changing the Document mode at all. It cause A LOT of errors. Tried setting it to 9 and 10, errors happened both times.
I could edit the fields in Chrome. However, IE 11 is the company standard and everyone uses it. So I still have the header (formlabel) not picking up the change in text.I noticed today that I also can’t add anything in the Custom CSS box by typing, but I can paste and delete code.
1. I attached a screen shot of the Custom JS tab.
There were no errors in the dev console.
I use Internet Explorer 11.2. The snippet worked on 4.4.3.15, but it’s not working on 4.4.3.34.
Attachments:
October 11, 2017 at 18:30 in reply to: Cascading dropdown values not triggering when "Set Value" DFFS Rule used #18410It’s a bit complicated, but here we go…
We wanted to use a cascading dropdown to populate field values from a list. We needed to limit the selection available to managers in the US. So, we created a list (Managers) with the managers profile names, IDs and hierarchy structure. The Managers list contains unique values.
When the New Form is opened, the manager dropdown defaults to the currentUser (permissions are set so only people on the Managers list have access to the New Form). A rule copies the currentUser to a manager_text field and “Cascade_1” uses the manager_text field to populate the field values AND a “manager2” field (used in another cascade).
Cascade_1 is where I’m having the issue described previously where the manager name appears in the first drop-down box, but the subsequent dropdowns do not autofill (the Autofill option is checked) and only display a blank. If I click the dropdown I see the (one) option available to select. Once I select all the subsequent options, the other cascade works.
As stated previously, if I replace the current SPJS_casc.js file with the previous version, it works.
Let me know if you need anything else.Carl
October 2, 2017 at 17:05 in reply to: Cascading dropdown values not triggering when "Set Value" DFFS Rule used #18332Hi Alexander,
I’m using the cascading dropdown tab.Carl
I’ve figured out the problem.
There was an issue with one of the Rules. DFFS v4.365 handled a rule differently than DFFS v4.2. After I fixed the rule, the forms loaded.Thank you for your help Alexander!!
The “_spPageContextInfo” did display the ListID information correctly.
After I verified the ListID was present, and while I still had the Console open, I opened DFFS edit mode and cancelled out of it again and I got the attached error.
I have another list using the same dffs files. I opened it with the Console open, and did not receive any errors.Attachments:
Here’s a screen shot of the header I’m dealing with.
Attachments:
-
AuthorPosts