Home › Forums › Classic DFFS › Setting ReadOnly PeoplePicker causes exception
Tagged: PeoplePicker, readonly
- This topic has 7 replies, 3 voices, and was last updated 3 years, 3 months ago by Rick Nichols.
-
AuthorPosts
-
-
August 19, 2021 at 06:54 #34323
Hi Alex,
Found a DFFS issue I hope you can help with.
Env: SP2010 (spjs.dffs.version 4.4.5.27 spjs.utility.version 1.352)An EditForm Rule (executed on form is ready) is fired to set a number of fields readOnly under certain conditions. This is the only rule in the form. Three of these fields (personA, personB and personC) are Person or Group type non-multiple, Person only, All Users. There is no reliance on any other rule.
If all three are included in the rule the “.join” error below occurs. If only personA is included then the form works. No other combinations will work. There doesn’t appear to be anything specific about the other fields which would single them out as an issue.
Thanks in advance.
MarkVM11024:1 Uncaught TypeError: spjs.dffs.beforeProperties[b].join is not a function
at String.eval (eval at (VM10062 DFFS_frontend.min.js:1), :1:42744)
at Function.each (bundle.js:4)
at Object.doReadOnly (eval at (VM10062 DFFS_frontend.min.js:1), :1:41611)
at Object.ruleMatch (eval at (VM10062 DFFS_frontend.min.js:1), :1:153750)
at Object.eval (eval at (VM10062 DFFS_frontend.min.js:1), :1:188990)
at Function.each (bundle.js:4)
at Object.loopOverRules (eval at (VM10062 DFFS_frontend.min.js:1), :1:188647)
at Object.init_triggerRule (eval at (VM10062 DFFS_frontend.min.js:1), :1:187504)
at Object.eval (eval at (VM10062 DFFS_frontend.min.js:1), :1:184565)
at Function.each (bundle.js:4)
at Object.triggerRulesOnLoad (eval at (VM10062 DFFS_frontend.min.js:1), :1:183950)
at Object.applyRules (eval at (VM10062 DFFS_frontend.min.js:1), :1:233929)
at Object.loadCustomJS (eval at (VM10062 DFFS_frontend.min.js:1), :1:200952)
at Object.loadDependencies (eval at (VM10062 DFFS_frontend.min.js:1), :1:202466)
at HTMLDocument.eval (eval at (VM10062 DFFS_frontend.min.js:1), :1:175405)
at i (bundle.js:4)- This topic was modified 3 years, 4 months ago by Mark Maconachie.
-
August 19, 2021 at 13:48 #34332
It’s hard to tell exactly, but I think this might be related to the userfields being loaded asynchronously and not being ready when the rule tries to pull the value from them to show the read only label.
You can try setting a delay on the DFFS loading in the Misc tab – try with 500ms and see if it helps.
Alexander
-
August 19, 2021 at 22:40 #34335
I will give this a try and confirm. Unsure if this matters but the issue does not occur using DFFS version DFFS_2020-05-10 and earlier, but does occur in all versions from version DFFS_2020-06-01 and any newer
-
August 26, 2021 at 23:54 #34364
The change to 500ms delay has improved the issue, so the issue does not occur 100% of the time. However as it is still occurring and so I have had to revert back to DFFS version DFFS_2020-05-10 for edit form as the error does not occur for this version and any earlier version
-
August 27, 2021 at 16:09 #34366
I have fixe the issue in cooperation with Mark Maconachie – not sure if you are working together, but I’ll release a new version that fixes this issue over the weekend.
Alexander
-
-
August 20, 2021 at 12:20 #34337
Thanks for the info – If it is possible to look at it in a test site it would be great. Send me some information in an email if this is an option.
Alexander
-
August 24, 2021 at 07:53 #34348
Hi Alex,
I have responded via email with a test list.
Thanks in advance,Mark
-
September 2, 2021 at 04:13 #34391
Thanks Alex, yes Mark and I work together and thanks heaps for the change it has solved the problem
-
-
AuthorPosts
- You must be logged in to reply to this topic.