Agree with Stephanie - there is not currently a way to do this, other than manually entering the retroactive location history for each new component.  

Or, we have played with the idea here of taking a 'day forward' approach; i.e. when you assign the new component its current location, enter a Location Remark something like "for previous location/inventory history see component 'a' ".  Combine that with a distinct Location Purpose - something like New Component Added - so you can easily spot and search on the 'fork in the road.'  If at some point later you come across a distinct need to report the full location history of one or more individual components, you could enter the retroactive histories if/when needed. 

Anyone see cons/issues with that approach? 

Kim



On Thu, May 2, 2019 at 7:22 PM Liz Byrne <[log in to unmask]> wrote:
Is there a way to create a component and retain the main object's location history for it?

To unsubscribe, send an email to [log in to unmask] with the following commands in the body of the email:

     signoff TMSUSERS

     //  eoj


You will receive a confirmation that your subscription has been removed.


--
Kimberly Koons, Presidential Libraries Museum Collections Officer
National Archives & Records Administration
700 Pennsylvania Ave., NW
Washington, D.C.    20408
202-357-5082
301-837-0873
To unsubscribe, send an email to [log in to unmask] with the following commands in the body of the email:

signoff TMSUSERS

// eoj

You will receive a confirmation that your subscription has been removed.