Suggest a new Idea

    • 3

      Update work order status/substatus when a booking is set to in progress

      Suggested by Heikki KangasNew 0
      Category: Field Service

      On the field service mobile app, when you update booking status to in progress, the work order system status does not update until a sync has been completed. In offline situations, the work order system status remains Open - Scheduled which gives the wrong status to the user. The status should update without requiring a sync in offline scenarios also.
    • 1

      Global search on all attributes and entities bing like

      Suggested by Gary TomazevicUnder Review 2
      Category: Field Service

      Multi entities and attributes search

    • 1

      Agreement Booking Setup's Recurrence Settings to draw from Entity Fields

      Suggested by Boris KlimovitskyNew 0
      Category: Field Service

      Currently, the only fields the Agreement Booking Setups default to are the Start Date and End Date of the parent Agreement Entity. The other fields: Recurrence Patterns and Range of Recurrence (except Start Date) all have to be entered manually on each Agreement Booking Setup. (and Recurrence Pattern XML does not appear to accept XML generated via Workflow) It would be helpful if they were instead drawing from explicit Agreement Booking Setup fields (that don't necessarily have to be displayed to Users), so that those fields could be prepopulated by organizational defaults or set by Workflows to reduce data entry burden for Users on each and every Agreement Booking Setup. For example, if a User is allowed to select a Weekly recurrence pattern and the company only works a Mon-Fri schedule, the Days fields could be preset by Workflow to prepopulate on the Booking Recurrence form, saving the User 5 clicks per Agreement Booking Schedule. The User would still have the option to override the defaults manually. If a User selects End Recurrence to be Never, After, or By, different fields would appear - for After, the Number of Occurrences, for By, a Date field. These would populate the appropriate fields in the Recurrence Dialog. This doesn't seem like a huge click savings, but consider that these fields could be prepopulated by Workflow and thereby saving considerable data entry.

    • 1

      Adding New Inventory Adjustment Product

      Suggested by Chad NelsonNew 0
      Category: Field Service

      How about adding ANIAP button that appears once the record is saved instead of having the user click on the arrow on the Adjustment Number then click on Product and then click on Add New Inventory Adjustment Product.

    • 1

      Creating Product Inventory

      Suggested by Chad NelsonNew 0
      Category: Field Service

      How To Create Product Inventory- Currently not natively visible on main menu. Creates confusion as to how to add Product Inventory.

    • 0

      Allow to create a work order for a contact (not account)

      Suggested by Jonas WautersNew 0
      Category: Field Service

      Field Service today only supports creating Work Orders for a Service Account. It would be great to also support Contact (so we can support the B2C scenario).
    • 0

      Customer Asset - Historical Records

      Suggested by Danny WiederNew 0
      Category: Field Service

      Customer Assets may change over time. They may be upgraded and become a different product, other field may change, they could move accounts so their external id changes etc. Currently if you look at any Work Order/Incident, it shows you the current asset data. So if you look at an old call and the asset has changed since, you get an incorrect picture. If you re-print a service report it will also show incorrect asset information.

      This ought to be changed so that the WO and Incident reflects the asset at the time the call is taken. Reports should also use this data instead of current data. This is a standard feature in other FS systems.

      Ideally an Asset's change history, including account and agreement moves etc, should be stored separately and accessible from the Asset record.
    • 0

      Option to default time to a time other than 8:00 AM on date/time fields

      Suggested by Audrey CarlsonNew 0
      Category: Field Service

      Would like the ability to define a default time that would be applied when a date is selected on a date/time control. A time other then the current 8:00 AM that appears. Would prefer a time of 0:00 or null that would force the user to enter an appropriate valid time.
    • 0

      Activity entity - Customize Filter on Field

      Suggested by Prune DufosseNew 0
      Category: Field Service

      The "Filter on" field is not customizable today. We can't hide it, or modify the list of filters. It is not always suitable for users.

      Can you make this field customizable in a future version please ?
    • 0

      Agreement Booking Setup's Recurrence Settings to allow Date/Time Fields

      Suggested by Boris KlimovitskyNew 0
      Category: Field Service

      Currently, if you examine the Recurrence Settings XML, the dates are just dates. That's inconsistent with the rest of the product, where dates are date/times. Trying to create Recurrence Settings via workflow fails because the date as dynamically set via Workflow is set as a date/time and there does not appear to be any way to strip the time from the date. Recurrence Settings should instead accept Date/Time fields as the rest of the product does; then workflow-set recurrence settings wouldn't fail.