The new designer. I know how to do it in classic, but having issues with the new way. 

I don't think this is currently possible.

The LFForm object has options for setting/changing the pagination button labels, but I don't see any event handlers related to page changes or the tabs.

The javascript on these forms is sandboxed so it can't interact directly with any form/page elements, only what is provided via the LFForm object.

I was thinking that was going to be the case. It means I will just need to put up with the code running way more than it needs to instead of at the one point it is actually needed to run. Or add a button and make it so the user must click that button to be able to submit.... I don't think the button method will be the best way. 

I agree. I would rather compile data into a table when the user goes to the next page rather than on field change of 18 different fields. 

I ended up using a couple buttons on the tab that grouped data is needed and until they click the button they can't submit the form. (this is a simplified description) 

Nice. I need that table summed up so they can sign off on it. So i can't trust the user to do it on their own.

I ended up just putting it on the other tab so they would never see the form jumping around every time they enter/delete data. Makes sense to separate the entry fields on one tab and the results on another. So far so good. Just not as efficient. I have noticed a trend in version 12 like that.

Oh, also I updated one of my environments to the latest Forms update. The fix to make modern designer collections load quicker actually slows it down. I have a conspiracy theory that LF dev is making on prem version worse and worse to nudge everyone to the cloud. Someone please prove me wrong.  



Ya no. Please, please, please try again. 

hmm that may explain why one of my forms did not do well when trying to convert it from classic designer to modern. I might try again to see if this fix, well fixed whatever was going on.

Could be. My scenario was that after 20 rows of a collection the form slows down significantly. Not sure if others reported the same thing but they filed it as a bug. So they could reproduce it in some capacity. Not sure if that particular bug would impact converting to the Modern Designer.... But there are quite a few other fixes that got rolled out in that update. I hope if goes well for you :) 

Hi @████████,

The Bug 655949 you highlighted is only aimed to fix a performance issue for Classic form designer, but you mentioned "The fix to make modern designer collections load quicker actually slows it down.", could you tell us if you are still suffering with performance issue on the new designer, or the fix on classic designer does not work? Please share.

sorry for the confusion, This was in the classic designer where the slowness still exists for me. I was referring to converting to modern designer as the next step, but there is a mountain of JQuery to convert to JavaScript which I was hoping to avoid. Also, it's not a guarantee.