Forum Replies Created
-
AuthorPosts
-
currently I am using Dynamic Forms for SharePoint DFFS Backend v4.4.3.10|CSS version: 4.37 / 4.37|spjs-utility version: 1.309
Thanks!
good day. working with cascading using multi select I find something to be cumbersome. When you select an entry and use the autofill if only one option present, it doesn’t work. It simply adds the one value to the Available options and not into the selected options forcing you to select them and add them to the Selected options.
It would be cool if I were able to select 2 or more options in the “Available Options” box and all entries in the second box just transferred to the “Selected options” box. This would allow me to hide the second field “Business Sponsor” in this case so the EU did not have to deal with it and I could still use the values in a workflow.
attached in this example you can see I selected BI/Analytics & reporting as well as EF DATA CAPTURE
in the Business sponsor box the corresponding entries, “bill and Lisa” are placed in the “Available Options” and not automatically into the “Selected options”. Hope I am making sense.
Attachments:
Now that I think about it if I had the code or function to hide a tab that would be awesome as well!
Good day Alex, I don’t see this anywhere but it would be nice if we had an option for setting an entire tab index to read only based on a rule.
CheersThank you sir.
it would be really nice to be able to copy entire sections. Example would be a check box that you can copy the heading, fields under it because you want to move the entire section up or down the form or maybe even move it to the edit form from new.
Cheers
Dynamic Forms for SharePoint DFFS Backend v4.4.3.42|CSS version: 4.42 / 4.42|spjs-utility version: 1.323
– forgot to include thissorry, here is the version I am using.
Dynamic Forms for SharePoint DFFS Backend v4.4.2.9|CSS version: 4.21 / 4.21|spjs-utility version: 1.279
– by Alexander Bautz / SPJSBlog.comone more picture to complete the argument.
you can see that the fields are visible until I click on the header.
Attachments:
I figured this out. it is in the page setup of Internet Explorer. Please disregard.
November 22, 2016 at 19:56 in reply to: Setting default {currentUser} on People Picker results in invalid entry #14225good day!
I used spjs.utility.userProfile(); to access the properties on the UPS. Unfortunately, most of the columns do not work. An example is I have to use {currentUser:EMail} instead of what the ups says is WorkEmail. I tried AccountName on both a text field and a people field. I am attaching a picture of my fields along with a snapshot of my console output. Any guidance would be appreciated.
Thanks!
cant delete this… found I was using currentuser instead of userprofile. nevermind this entire comment.
- This reply was modified 8 years, 1 month ago by William Summers.
Attachments:
Any ideas on the above per chance?
QQ. I have a people field that is set to display workEMail. In the list view as well as the dispform it shows the email address. However, in the editform it shows the resolved username. The email functionality requires it to be an email in the people field.
I want to email from the editform using a people field. Currently, I have a rule that sets the value of that people field. {setCurrentUser:Email} no matter what I have tried, in the editform the people field resolves the name to lastname, firstnameThanks
it will. I am requesting that it be removed. It affects almost 20k sites and is crazy… before my time it was placed but no reason any more.
update: last one….
All of my issues can be traced back to the masterpage loading an old version of jquery. That being said, maybe this will help others.debugging lead me to this. masterpage loads old version of jquery my company uses. I used a CEWP and in the source placed <script src=”/sites/yoursite/spjs/dffs/plugins/jquery.js”></script> to point it at the correct one. Wow what a long thread for something that is our own fault….
-
AuthorPosts