We are looking at bringing our products into the Field Service module of Dynamics 365. Our products can move between customers and they have unique serial numbers to identify them.
Eventually we would like to go down the IoT route and get readings from our products. We are considering using the Customer Asset entity of the Field Service app. It looks like we would need to add in a new serial number field to the entity but everything else should be ok for us.
We want to be able to look at an asset and be able to see the history of that asset, e.g. it was installed at customer X between 1st June 1999 and 25th September 2006.
Not sure how we keep this history so one idea we had was instead of having one asset which we move around between customers, could we put an end date on and then deactivate any deinstalled asset and create a new asset with the same details but at the new customer? We would then know any asset which is active is the one in the field and the inactive ones are the historic products.
We are also considering using the parent asset field to structure the subcomponents of each product. We would need to make a copy of all items under the master asset then deactivate the original assets.
Dpes this sound feasible? Is there an alternative way we could do this?