Uploaded image for project: 'Providence'
  1. PROV-2054

Current location not updating for movement based storage location tracking

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects versions: 1.6.3
    • Fix versions: None
    • Components: Providence Libraries
    • Labels:
      None

      Description

      We've got movement based storage location tracking, and cannot get the current location (what's shown in the inspector and also in the current_loc_class, current_loc_subclass and current_loc_id fields in `ca_objects`). The relevant relationship types and

      ```
      # Location tracking options
      object_storage_location_tracking_relationship_type = storage_loc
      movement_storage_location_tracking_relationship_type = moved_to
      movement_object_tracking_relationship_type = part
      record_movement_information_when_moving_storage_location = 1
      movement_storage_location_date_element = removal_date

      current_location_criteria = {
      ca_movements = {
      movement = {
      date = pickup_date,
      template = ^ca_storage_locations.hierarchy.preferred_labels%delimiter=_➜_
      }
      }
      }
      ```

      The only way the current location gets updated is to manually associate an object with a particular storage location.

      Please let me know if you need any more information to replicate this bug.

        Attachments

          Activity

            People

            • Assignee:
              Former user (Inactive)
              Reporter:
              Kehan Harman
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: