[SteveE]

Sweet! That did it. Thanks!

[SteveE]

Can I trigger the cancel button functionality instead?

[SteveE]

I really like this and can get it to work on my test form. However on my production form the “back” history shows the same entry multiple times so it doesn’t redirect. It could be because it takes time to load or there are other timeouts on it. I’ve tried to add a timeout but I don’t think it will matter because the “back” history is loaded with the same form. I guess I could redirect it somewhere else, but is there any way to get it to go back to the view they were at other than the “back” history? Maybe something with the source in the url? Thank you!

[SteveE]

I get that, but you can’t add a CEWP to a modern list view. There’s no “Edit Page” option.

[SteveE]

How did you even add a CEWP to a modern list view? If you switch it to classic experience and add a CEWP to a view it works. That’s how I have mine set up.

[SteveE]

If you are using modern list views, I believe it only will work in the classic list view.

[SteveE]

Are you sure you have the link set up correctly? It should be in your DFFS setup folder. Mine is in https://mysite.sharepoint.com/SPJS/DFFS/vLookup_ListView.html. That’s the link you have to add to the content link in your CEWP.

Then you have to add the vLookup column to the view so that it knows where to show the information.

[SteveE]

Set date in new field based on another field.

function SetDate(){
    var StartDate = spjs.utility.getDateFieldAsDateObject("StartDateField");
    spjs.utility.setDateFieldFromDateObject("EndDateField",StartDate,14);
}

[SteveE]

Are you sure you changed the rule in EditForm vs. what you had in NewForm? My guess is that it is writing the field again and it is now blank. Have you tried to recreate the read-only rule in EditForm from scratch, only using the read-only assignment?

A screenshot of the rule in EditForm would help.

[SteveE]

Sweet! Yeah it’s a lot of trial and error and using the dev definitely helps along with inspecting the elements and trying different options (min/max). Defining the .ms-formlabel helped me out a lot too. That used to not matter so much but with recent changes in the browsers it’s been necessary.

[SteveE]

First make sure the Side by Side settings box “Stretch side by side fields…” is checked.

Second make sure you are using the latest dffs. I found some errors a couple of versions ago that Alexander fixed.

Finally, it is a lot of trial and error with the css. Here’s some sample css that you can play around with that works to remove the orphaned lines.

.ms-formlabel{
    width:190px!important;
}
.sbs_tdIndex_1{
    width:325px!important;
}
.sbs_tdIndex_2{
    min-width:250px!important;
}
.sbs_tdIndex_2 .ms-formlabel{
    max-width:125px!important;
}
.sbs_tdIndex_3{
    max-width:290px!important;
}
.sbs_tdIndex_3 .ms-formlabel{
    width:125px!important;
}
.sbs_tdIndex_4{
    max-width:290px!important;
}
.sbs_tdIndex_4 .ms-formlabel{
    width:125px!important;
}

• This reply was modified 2 years, 7 months ago by SteveE.
• This reply was modified 2 years, 7 months ago by SteveE.

[Author]

Posts