Jump to content

Unable to save requests Details section - Site field mandatory


Recommended Posts

We appear to be experiencing an issue where we are unable to save the Details section of a request once it has been edited.  The option for Save is there, however it will not allow us to select this.  Has anyone else experienced this issue?

Link to comment
Share on other sites

We've had users report this today as well. Looks like Sites field is now required which it wasn't before and if you go on the Details Form Designer you can not toggle it being required or not.

Is this an unwanted change?

Link to comment
Share on other sites

We asked development to look into this. If the site is not required on requests you can choose to temporarily hide this field from details. Might or might not be a suitable workaround.

Link to comment
Share on other sites

  • Victor changed the title to Unable to save requests Details section - Site field mandatory
2 hours ago, Victor said:

We asked development to look into this. If the site is not required on requests you can choose to temporarily hide this field from details. Might or might not be a suitable workaround.

Hi Victor, unfortunately not as this would mean having to alter the forms on each of our Service Profiles.

Link to comment
Share on other sites

Also affected here too.  Site is not always captured, present or required but we do require the ability to update the External Ref No without having to add the Site.

Link to comment
Share on other sites

Hi 

We are also experiencing the same with site field, we usually want to leave it blank and only fill it in if the laptop is in the building so in stock so it is causing problems for our teams.

Helen 

 

Link to comment
Share on other sites

+ 1

Not a huge impact as we've only got one open ticket without the site set (no idea why it wasn't set by the self service capture, user is set up correctly) - can't update the request and complete our process for this one though as the site selector isn't working. 

Link to comment
Share on other sites

Morning, 

We are having the same issue here which is causing a lot of problems for our teams using Service Manager. Will await further information. 

Link to comment
Share on other sites

Just for info - We have this too. Also in the Asset forms

 

Link to comment
Share on other sites

Hi @Luke @Ann

Sorry to hear that. Would it be possible to try and refresh your browser's cache? That may help with the issue. Please let me know if it helps or not

Thanks :) 

Link to comment
Share on other sites

It's still not fully resolved for us, but I have done a bit more investigation. 

Our sites didn't have a company set against them: 

image.thumb.png.51d508be4402b22bd70d031e8db5c722.png

But I can see that the call to smGetSites includes a companyId param (don't know if this has changed but suspect it has?): 

image.png.f8063e166c383d60103a98dd717f2bf2.png

And the response returns no results with a search string I'd expect some: 

image.png.3ecdc471710347e5fa8f3403fd40a358.png

If I save a company against the site definition I can retrieve them which resolves the immediate issue.

Am I right in assuming that: 

  1. Tickets where the customer has a 'Home Organisation' set this is passed into the smGetSites call as a param to filter the list
  2. Tickets where the customer has no 'Home Organisation' this isn't passed into the call and we get the full list (filtered only by whatever's typed into the field)

We have users across 2 sites with their home organisation set to a different 'company' to get self-service branding/content correct, assuming the above is correct I'll have to check if this will cause any issues with how we set sites (some tickets are passed between sites) - I don't want to create duplicate site definitions for different companies as this will break a lot of widgets/dashboards that are looking for a specific site, and we can't add multiple companies to each site definition. 

Thanks, 

Luke

Link to comment
Share on other sites

Hi @Luke

Apologies for the delay in getting back to you regarding this. 

After investigating this, it seems to be a different issue to the one initially raised. I'll raise this as a new issue with the development team so we can try and understand it better

Kind regards

Mohamed

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...