Forum Replies Created
-
Posts
-
I got your script to work, this is what I came up with after tweaking it. Notice that I had to call the function for every peoplepicker. It works though.
~~~~
function peoplePickerChanged(fin){
var currPPvalue = spjs.dffs.beforeProperties[fin];
console.log(currPPvalue);
if(currPPvalue.length === 0){
console.log(fin + ” field is empty on form load”);
spjs.dffs.hideFieldsByRule(fin);
}
setInterval(() => {
let val = getFieldValue(fin);
let isResolved = spjs.utility.getFieldValue({“fin”: fin, “key”: “isresolved”});
if(!isResolved.includes(false) && String(currPPvalue) !== String(val)){
currPPvalue = val;
console.log(currPPvalue);
console.log(fin + ” changed to”, val);
if(val.length === 0){
console.log(fin + “is empty”);
}
else {
spjs.dffs.doReadOnly(fin);
spjs.dffs.unhideFieldsByRule(fin);
}
}
},1000);
}
peoplePickerChanged([“Employees”]);
peoplePickerChanged([“Employee”]);
peoplePickerChanged([“NewAM”]);
peoplePickerChanged([“Manager”]);
peoplePickerChanged([“Agent_Name”]);
peoplePickerChanged([“CenterPOC”]);
peoplePickerChanged([“CurrentAM”]);
peoplePickerChanged([“NewManager”]);
peoplePickerChanged([“Center_Sales_Manager”]);
peoplePickerChanged([“NewDirector”]);
peoplePickerChanged([“CurrentManager”]);
peoplePickerChanged([“CurrentDirector”]);
peoplePickerChanged([“EmployeeTrade”]);
peoplePickerChanged([“TrainingPlacement”]);
peoplePickerChanged([“ApprovedByManager”]);
~~~~Attached you will find the results of the console logs from your script. This is very interesting, and I cannot explain it. Notice that the logs never say “The field is empty on form load”. Rather, it’s saying that the fields are CHANGED to empty, and then seconds later, says they are changed to their current values. This is on Edit form. Those fields have values in them. When the form is loaded, they have values, I don’t know why it says they were changed to blank, and then just 1-2 seconds later says changed to what they actually are. Notice that DFFS load time tracker logs in between these actions. Something is off here, I can’t figure out what it is, but it’s a timing issue with something. There are no rules clearing these fields out.
Attachments:
Thanks, I will try this. Just so you can see what I’m talking about, here’s an example. I have the delay load in the MISC tab set to 5000 ms and still you can see that the people pickers that get set to read only are showing blank, even though the actual field has people listed in them. Fields in this screenshot are Completed By and Employees.
Attachments:
Awesome! Yeah for the to-do list, I really only need it to be a visual thing, not an actual SP field or anything like that. I plan to use it as a visual reminder for my Project Management team to easily track and make sure they’ve done x,y,z and they can check off once they’ve done it.
> Cascading dropdowns are already supported – look at the user manual for details.
I apologize! I didn’t fully review the documentation; I expected to see it as a tab module like in Classic. My bad!
> I’m unfortunately still not able to recreate the issue you describe with all viewFields from the Build the table shows in the Add new item tab. Are you maybe copying or cloning the vLookup config prior to this happening?
No, here is the situation and the exact way I get it to happen:
1 – create your vLookup config and set it up as normal. Have the “build the table” filled out and with your date field do a customizer function that uses the function I posted above, and then have the “Add new item” setup with the prefill fields. For me, I had a child list with vLookupProjectID (single line of text) and ProjectLookup (lookup column in child list). I would set vLookupProjectID to [[fieldValue:_DFFSID]] and I would set ProjectLookup to [[item:id]]
2 – everything should work normally right now. You should see your table and you should be able to add a new item with the prefilled values properly.
3 – go into the vLookup config, and remove the customizer function
4 – you should now get an error “Customizer function not found” when you go into the item and view the vLookup table
5 – go back into vLookup config, and the only thing you can do is delete the field from the table and re-add it to get rid of that error.
6 – go look at the table, things should look normally again, but now click on add new item… is your pre-fill values still working? Mine don’t.
7 – go back into vLookup config, and you should see that the pre-fill values section is totally different and missing the pre-fill references.
That’s the best way I can explain it.
—
## Another new request if possible for a future release ## – would it be possible in a rich text field or maybe in a custom drag/drop element where we can have a checklist functionality? Like what you often see in OneNote. I’m creating a project tracker app, and it’d be awesome if I could dynamically add checklists into a rich text field so I can allow my team members to simply check the box when that action has been completed. Refer to OneNote and see the “To Do” checkbox for the functionality I’m asking for.
I solved for the timezone issue by adding a Customizer function to the field in the vlookup table.
function vLookupDateFormat(item, field, config) {
if (item[field.fin] !== null) {
var d = new Date(item[field.fin]);
return new Date(d.getTime() + 6 * 60 * 60 * 1000).toLocaleDateString(); //the + 6 (hours to add) * 60 * 60 * 1000 fixes an issue with the dates not displaying correctly for anyone not in Central Time due to DST. Note that this will change the timestamp, but I don’t care about the timestamp as I only show the date value.
}
}However, I recreated a previous issue I reported with vLookup in Modern DFFS I’d like you to look at.
In the build table section, I had the customizer function before and I removed it. Saved the form and then looked at the item and it said “Customizer Function Not Found” but I had no value in the Customizer Function section for that field in the vLookup configuration. I couldn’t get that error to go away, so my only choice was to remove the field from the build table config and re-add it. When I did that, I saved the form, and the error went away. However, when I went back into the vLookup config, and I went to the “Add new item” section, all of the Prefill field values I had set completely changed. It was using the same fields from the Build the Table tab, and I don’t use any of those fields.
Build table tab has:
Title
StartDate
EndDate
StatusAdd new item tab has:
vLookupProjectID (single line of text) that I set to [[fieldValue:_DFFSID]]
ProjectLookup (lookup column in child list) this I set to [[item:id]]When I removed StartDate and EndDate from Build table tab, and I readded them, I saved. Then I got a report of someone trying to add a new item where ProjectLookup and vLookupProjectID were not getting set automatically. So I go into the config and I see that the Add new item tab was completely changed. It showed the same fields as the Build Table tab. This has happened several times.
So I found the underlying problem, and it’s daylight savings time. The way that date field is brought in, is not respecting daylight savings time.
Found another issue this morning. On vLookup build a table, I was just notified by a user in a timezone that is 1 hours behind my own (I’m in Central Time United States, they are in Mountain Time United States). I am bringing a date field into the table for the vLookup. For me, the dates look correct. For the coworker in the other time zone, the dates are off by -1. If that same user goes to the list referenced in the vLookup and looks at the date values in the list, the dates show correctly for them. The issue is exclusively in the vLookup table.
I have tried both onload only and onload and onchange. It’s not that it doesn’t work, because it does… just not consistently. The rule evaluates before the peoplepicker resolves. What I noticed is that onchange it doesn’t revalidate.
Setup is the rule for PeoplePicker is equal to [blank] and then I don’t do anything with it at that point. What I do is I reference that in a Linked Rules and Functions section of other rules and I have the box checked so that a change in that rule will revalidate the parent rule. That’s where I’m seeing the inconsistent experience.
Hey Alex thanks for doing what you can with these, I know a few of them were going to be big and likely long term, if at all so no worries!
<i>Can you give me some more information about adding the class to the fields? – do you mean like adding a classname in the “container styling” property of a field?</i>
Yeah so basically I want to be able to put in a classname that might help me style those fields easier. The more I think about it though, maybe it won’t. You can disregard this.
However, I do want to call out a couple things with vLookup. I’d like the ability to easily control width of fields in the “build the table” section. I have some fields, mainly when it’s multiline text, it will take up a ton of space and leave the other columns squished in the table.
Also, number fields are causing an issue. I have number fields in the vLookup that are whole numbers but displaying with a decimal with many numbers behind it. Like 7.999999999999 or something crazy.
Lastly, can we get some basic formatting options for some fields that can be configured in the properties to save time from having to code for it in JS? Having “no-wrap” comes to mind, and also this is a big one — date formatting. Can we have various default options to choose for how to format dates. Long Date, Short Date, Date and Time, Date Only, Time Only, etc.
Just throwing out ideas, appreciate all your work!
Also, I’ll be emailing you soon about that other thing we’ve discussed. I need to send you a tip soon too, it’s been awhile buddy!
I’ll try to install the updated version tonight when no one is working in the list and see if I can identify any specific errors. You mention turning off sync, but what’s interesting is that’s not an option on this list. There are other lists where it is, and I have turned it off, but not on this one in particular. This isn’t the only list like that either, there are others where sync is not listed. It was still loading with new modern UI when I updated DFFS, it was not reverting back to old modern UI. Ideally getting them to co-exist would be great!
I reverted back to v1.0.64 which is the last version I had installed. That put DFFS back on the list menu and restored my form. This is on a production site, so I couldn’t afford to leave it on and troubleshoot. I will try and find a low traffic site I can put it on and see if I can help find the issue.
I have a totally different problem. I have deployed v1.0.66 and now DFFS isn’t showing up at all. New, Edit, Display, doesn’t matter. DFFS button doesn’t even show in the list menu bar anymore either. I’m going to have to revert back.
