[SteveE]

Hey Alexander,

I’ve just barely started testing the new version so I’m just going to give you a few things from what I’ve seen.

I’m not having any luck getting vLookup to work. It doesn’t show the “New” button and the table isn’t visible but I do see the “header” which shows on the left side. I put a filter in but it’s just blank – the table isn’t there.

I can still add Created By and Modified By fields even though they don’t work.

It might help to see a “Save” button on the vLookup config. Even if it’s already saved, maybe it just closes that section.

Similarly when you click save, the dialog would be helpful if you could close the dffs configuration screen from there, rather than having to go back to the top right to close it.

I do like that the details pane is fairly locked down. However, if you click the “edit all” hover that you see, and then you click the back arrow, you can see the activity more detailed and there’s a link that says “you created test”. That link will let me go to a details pane view where I can edit the item without dffs. Sounds confusing (it is) but I can recreate it.

I also am wondering about the dffs link. I’ve seen it on someone else’s computer and didn’t want to draw attention to it, but how do we control access to edit the form? Is it strictly in the password configuration? This is tricky because it shows that link on all forms even if they are on the old configuration so I worry about a conflict there.

I’ll keep testing when I have time.

[SteveE]

I say that and then it goes away. Weird.

[SteveE]

I’ve upgraded to the latest release and I’m still seeing this error.

[SteveE]

That’s great news!

Regarding the details pane: is there some code you can share to use that with the older dffs? Also one thing that is kind of important is if you are hiding something in dffs, it’d be great for the details pane to also hide it. The ordering and tabs are understandable to not be able to do it. But if I have sensitive information I’m hiding based on a rule, I need to be able to hide it from the details pane. OR can we just disable the details pane completely? Honestly that would solve a lot! Or maybe severely limit the fields and information that shows.

I know this is an early version, so I wasn’t expecting all the functionality from your years of developing the older version. I was just giving you the feedback you requested for what I see as important features that I saw missing.

This is really great work. It will take some getting used to and I’m happy to test it when I have time. It’ll be interesting how you plan on pushing out updates.

[SteveE]

This is really cool and interesting. I’ll keep digging around into it. Here are some quick initial thoughts.

Love/Like:
– The drag and drop attachments built in!
– Default of hiding the left navigation menu
– Dragging fields to move them is easy and seeing the “grid” type of layout helps for designing
– Preview form
– Simple and clean

Missing:
– Something that I miss is the copying of the form from New to Edit to Disp. Usually when I build something I start with one form and go from there if something is different in the next form.
– Along these lines – backing up the configuration and using development mode are super important.
– I like being able to quickly switch from the various forms with your buttons at the top in the old version
– I really like the field list in the old version so I can make sure I’m using the correct Field Name for various things like custom JS. Not completely necessary but it’s nice
– vLookup config
– Searching rules for fields or text. Very helpful when I have so many rules
– Grouping things for rules. I like being able to tag all of the fields with one group and then, for example, require everything based on that group

Bugs:
– You can type the created and modified by fields in NewForm but it doesn’t actually work
– In NewForm it shows the ID field but it hasn’t been created yet

The biggest problem of all has nothing directly to do with DFFS and is the default modern SharePoint list view. The Details Pane ignores everything in DFFS and allows users to view and edit fields. I’ve never been able to figure out how to get rid of it so it forces me to use classic views for most of my lists to prohibit someone from editing or viewing an item and not following any rules or ordering or anything else I have put in place using DFFS. This will be a major reason I can’t use this version for many of my lists…yet.

I love your work and this is quite an undertaking. Great job!

[SteveE]

For EditForm:
In Custom JS add this
jQuery(“#dffs_Dropdown select”,”dffs_Dropdown2 select”).css(‘background-color’,’#ffcccc’);

For DispForm:
In Custom JS add this
jQuery(“#dffs_Dropdown td.ms-formbody”,”dffs_Dropdown2 td.ms-formbody”).css(‘background-color’,’#ffcccc’);

In DispForm it highlights the entire cell so you may want do change it to just ‘color’ and you’ll just change the color of the text.

[SteveE]

I’ve had this problem before. I found that running any other scripts on the page have to be contained inside of the web part that has the chart. I think it’s a page timing issue.

[SteveE]

Make sure they have permissions to read the spjs and associated installation libraries and lists.

[SteveE]

Agreeing with Keith on this as I would make a field or script that combines the three fields and then check against them.

Instead of using the native duplicate check you could use a presave. Something like this:

function dffs_PreSaveAction(){
var Pass = true;
var res = spjs.utility.queryItems({
“listName”:”The List To Check”,
“query”:”<Where><Eq><FieldRef Name=’Title’ /><Value Type=’Text’>”+getFieldValue(“Title”)+”</Value></Eq></Where>”,
“viewFields”: [“Title”]
});
if(res.count > 0){
Pass = false;
}
if(!Pass){
spjs.dffs.alert({
“title”: “”,
“msg”: “There already is an entry that matches this.<br><br>Please edit the existing entry.”
});
return false;
}
return true;
}

[SteveE]

That works! Awesome as always!

[SteveE]

Hi,

I’m kind of confused. You have a parent list that contains the user and if they are hourly/salary. You are creating a child. Why not have them create the child based on the user in the parent and then populate the field you want in the child like this https://spjsblog.com/vlookup-for-sharepoint/vlookup-user-manual/#Prefill_values_in_child

Cascading lookup does work also, and does not require another selection. Once you pick the first field it fills out the next one: https://spjsblog.com/dffs/dffs-plugins/spjs-cascading-dropdowns/#Set_field_value

You have another option that might work depending on your situation. You could try the autocomplete function. I don’t think it applies but it might work: https://spjsblog.com/dffs/dffs-plugins/spjs-autocomplete/#Autocomplete_in_a_text_field

[SteveE]

Hey TJ,

First make sure you follow the full installation manual: https://spjsblog.com/dffs/dffs-installation-manual/. This includes the installer page.

Once that is done, yes, you create a custom list. Create the columns you want in that list. Then you go to that installer page and find the list and install dffs on the list.

Then you access the configuration by clicking the link at the bottom of the form. Usually you start with NewForm (clicking the New button) and start configuring that.

There’s a ton of options and they are explained in the user manual. https://spjsblog.com/dffs/dffs-user-manual/ It can be as simple or complex as you need. Have fun!

[SteveE]

Hello,

I’m a little confused by the question. Column B is Yes/No choice but Column A is a text field. If column A is anything besides Yes or No it won’t work. If it’s always Yes or No, why not set up a rule in dffs, use the Set field value section and reference the column using brackets {ColumnA}?

[SteveE]

I’m pretty sure you’ll need a new license so I’d reach out to Alexander directly.

[SteveE]

Can’t you just enable it in the admin center? That’s what I did.

[Author]

Posts