Update V2.1.42 and V2.1.43

Hello,
We are currently using Version 2.1.41 and want to update our Plumsail Helpdesk to Version 2.1.43.
There is a note stating: "This update requires manual actions. You need to run the installation wizard in Repair mode before starting the upgrade. Then start the upgrade again."

Additionally, there is a widget modification mentioned in update 2.1.42.
Do we need to create a backup or perform any other preparation steps besides running the installation wizard in Repair mode?

We are currently using the widget. Will it function normally after the update, or will we need to make manual adjustments?

Best regards
David

Hello David! No back-ups are required. Running the wizard in the repair mode should be enough. If not, the update logs should throw an error with further instructions. The existing widgets will continue working as usual. But if you wish to switch to the new version (which we recommend), you will need to create a new widget configuration after the update and replace the old one.

Hello,

A few weeks ago, we updated the Helpdesk version to the latest release. However, today we encountered issues with the widget in both SharePoint and Teams. It failed to load correctly, either displaying a blank page or showing the message "An unknown error has occurred. Please try again later." In some cases, the widget loaded after a delay, but these instances were exceptions.

We have not made any further changes to the widget since the update. I followed the instructions from your documentation (Add widget to SharePoint site — HelpDesk for Microsoft 365, MS Teams, and SharePoint 1.x documentation)) to configure it.

To resolve the issue, we attempted several steps:

  • Re-uploaded the Helpdesk SPFx package to the app catalog
  • Removed and re-granted API access
  • Created new widget configurations using both the default form and the form from our previous widget
  • Updated to the version 2.1.44 today

Despite these efforts, the same error persists, and the widget continues to show a blank page instead of the form for creating tickets.

Could you help us identify the cause of this issue? Additionally, can we use the modified form we created for the previous widget and link it to the new widget, or do we need to create a new form from scratch?

Thank you for your support.

Best regards,
David

Hi,

I want to provide additional information on the last answer of my colleague.

The granting of API-Access throws an error, even if the access ist mentioned as granted after the error:

Also when I try to give API Access via PowerShell after deleting the granted access again and uploading the package, there's an error, but after the error the API-Access is shown as granted in the SPO API-Access page.

The page where the new widget is placed (where the old one was functionally until friday last week) still shows no widget, after many seconds there's the "sth. went wrong" message. I exported the console-log of the Edge-Browser. I also tried it in an inPrivate window.
Tenant.com-1741013414354.log (139.2 KB)

Hello, I have passed the information to developers for research. But I could not load the browser console logs. Could you reproduce the issue with the widget in incognito mode, re-collect the logs and save a HAR file too (on the 'Network' tab of development tools)? Then send the files in a private message to me. Also please specify the URL of the HelpDesk site which the widget relates to.

We published a fix. Please clear browser cache and check whether it helps. If not, please provide the information requested above.

Hi,

the Fix solved our problem. Thank you very much.

Now we wanted to include our Pumsail Forms formula (with modified fields) into the widget by placing it's ID in the widget backend.

It shows the formula as before but when I click on Submit there's an error thrown:
1

I exported the .har File for the new error, maybe you got a soution for this too. The file is coming via PM

Thank you for the confirmation regarding the first issue! Please export the forms you tried to apply in the widget configuration and save the browser console logs, share the files in PM for research.

Hi,

I found out that in the new widget I must use fd.beforeSave(fd.helpDeskWidget.Save); instead of

fd.beforeSave(fd.helpDeskWidget.AddTicket); like before.

Now the formula is saved, but only to plumsail forms, not to the HelpDesk in SharePoint itself.

Configuration of the Widget:

The Definition of the Plumsail Widget comes via PM.

Dear Markus,

if you modified the form in your Plumsail account and its ID is saved in the widget configuration, all changes will be reflected in the widget automatically. When creating custom widget form, you need to customise the default one and do not delete the default parts. You can find the default forms in this article.

The form you shared lacks also this part of the code: fd.helpDeskWidget.Init(fd.helpDeskWidget.FormTypes.NewTicketForm);

Please try to put these rows at bottom of your custom code:

fd.helpDeskWidget.Init(fd.helpDeskWidget.FormTypes.NewTicketForm);
fd.beforeSave(fd.helpDeskWidget.Save);

Do not forget to delete fd.beforeSave(fd.helpDeskWidget.Save); at the top. If that does not help, please share the current form version, fresh browser console logs and network data (HAR) collected in a private mode.

Hi Evgeniy,

unfortunately it didn't work.
The Logs and json of the formula I will send via PM.

I also commented the following code at the beginning because I wasn't sure if there might be a problem with the GUID mentioned, but this also didn't work.

//fd.beforeRender(function(){
//    var fd = new Plumsail.Form('#plumsail-form-x8s2', 'e7dc3f5b-222b-4822-95d4-2b944a5a246a', {
//        culture: 'de-DE',
//        language: 'de-DE',
//});
//
//})

The Ticketsubmissions arrive at the plumsail form, but not in the SharePoint Helpdesk-List.

@markus, the provided HAR file contains this error:

There was an exception while writing field ErstellungsDatum. Verify you're using the correct InternalName value for the field you want to write to.

Please find an internal name of the required column in the 'Tickets' list and use it to name the field in the form. If the issue persists after that, please share again the fresh form, browser console logs, and a HAR file.

Hallo Evgeniy,

we deleted the field from the plumsail forms and now it works.
But that should not be so, because if you have a look on the SharePoint list, the field was set up correct.
{30C4AAA5-C652-4983-AE29-ADFD01977D05}

Maybe there has something changed in the programming functionalities with the new widget?
The only thing which stood in the js-Code is the following:
//Erstellungs Datum speichern
fd.field('ErstellungsDatum').value = new Date();
fd.field('ErstellungsDatum').hidden = true;
fd.field('ErstellungsDatum').widgetOptions = {
format: 'dd.MM.yyyy',

I will enquire on that and get back soon.

Markus, now your form should work but developers advised to send the data value in ISO 8601 format.