Field Service

Get Involved. Join the Conversation.

Topic

    Antero Makinen
    Change Activities in GroupsAnswered
    Topic posted February 7, 2019 by Antero MakinenRed Ribbon: 250+ Points, tagged Configuration, Dispatch Functionally 
    34 Views, 2 Comments
    Title:
    Change Activities in Groups
    Summary:
    Updating fields with mass change works stupidly
    Content:

    Hey, 

    We noticed a quite stupid way in the "Change Activities in Groups" feature (https://docs.oracle.com/en/cloud/saas/field-service/18d/facmu/working-with-activities.html#t_changeActivitiesInGroups).

    We have multiple fields in the Change Activities in Groups feature, but most of the time we only want to change one or two of them instead of all the fields. Now it clears the fields that have no information inserted in the "Change window", please see the attached image for more clarification.

    I made a quick fix for this by removing all the other fields but the one that is most used.

    I just want to ask, is this working as intended that it clears the fields, or is there a bug? Let me know how you guys use this feature.

     

    Version:
    18D
    Image:

    Best Comment

    Zsolt Tolgyesi

    Hi Antero,

    IMO because there isn't other option to delete the value of a field with that way, then this is the expected behavior.
    You can put this into the Idea Lab for an enhancement for future releases, or other way to enrich the documentation with a comment about this limitation.

    I think changing ZIP for a group of activities isn't a logical things to do, while client address need to track in source system.

    Regards,
    Zsolt

    Comment

     

    • Zsolt Tolgyesi

      Hi Antero,

      IMO because there isn't other option to delete the value of a field with that way, then this is the expected behavior.
      You can put this into the Idea Lab for an enhancement for future releases, or other way to enrich the documentation with a comment about this limitation.

      I think changing ZIP for a group of activities isn't a logical things to do, while client address need to track in source system.

      Regards,
      Zsolt

      • Antero Makinen

        Thanks Zsolt, 

        Yeah, at least the documentation should have a mention about this. And you are correct about changing ZIP (or even phone numbers or customer number) with mass update isn't wise. We haven't used this feature yet, and those fields have been there probably for some testing reasons. That's why the fix I made for this is fine, because all the other fields weren't in use anyways.

        We'll continue using mass update with only one field, and hope that we don't need another field in the future.

        I'll check that Idea Lab later and probably send a suggestion there. I might have some other ideas too. :)