Change in Visit window times for one date set is changing for all the data sets when data sets are cloned
Trailblazer Community

Change in Visit window times for one date set is changing for all the data sets when data sets are cloned

Maps Advanced

Last updated 2021-08-11 ·Reference W-9463965 ·Reported By 2 users

Fixed

Summary
Change in Visit window times for one data set is changing for all the data sets when data sets are cloned. The issue is always reproducible with cloned data sets in the same visit plan or with the data sets which are the part of cloned visit plans

Repro
Found in SF Maps v232
A: Cloning the data set

Create visit plan, set visit windows times in data set and save the data set
Clone the data set
Edit and change visit windows times on cloned data set
Review original data set, note visit windows times have now changed.
This also happens if you edit the original data set's visit windows time and it then changes the times in cloned data set.


B: Cloning the Visit plan

Create a visit plan and save after adding all required data.
Clone the visit plan
Change visit windows times on cloned visit plan - data set
Review original plan's data set, note the visit windows times have now changed too
This also happens if you edit the original visit plan's data set visit windows time and it then changes the times in cloned visit plan's data set.




Expected Result: Visit windows are independent of each other when used in different data sets/visit plans, even if cloned.

Actual Result: Visit windows change on cloned and original data sets of same plan and/or cloned and original data sets when plan is cloned.

Workaround
Manually create new data set versus cloning

Updates
Resolved in v232.7.1

Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.