# Artifact name with script update module **URL:** \ **Category:** General Discussions\ **Tags:** update-modules\ **Created:** [January 11, 2020, 8:13pm UTC](https://hub.mender.io/t/artifact-name-with-script-update-module/1428 "2020-01-11T20:13:44Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![edocklea](https://avatars.discourse-cdn.com/v4/letter/e/91b2a8/32.png) [@edocklea](https://hub.mender.io/u/edocklea)\ **Post date:** [January 11, 2020, 8:13pm UTC](https://hub.mender.io/t/artifact-name-with-script-update-module/1428/1 "2020-01-11T20:13:44Z")
Is it possible to prevent the artifact\_name from changing when running a script from an artifact created using the script update module? I’d like to be able to deploy a script artifact and have it run without changing the current artifact\_name (and the “Current software” field under Devices in the Mender server dashboard). Thanks. ---
**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\ **Post date:** [January 13, 2020, 8:09am UTC](https://hub.mender.io/t/artifact-name-with-script-update-module/1428/2 "2020-01-13T08:09:42Z")
At the moment no. I know there are some discussions regarding how to handle artifact naming and history but I don’t think anything is actively in progress. @kacf can you comment? ---
**Author:** ![kacf](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kacf/32/146_2.png) [@kacf](https://hub.mender.io/u/kacf)\ **Post date:** [January 14, 2020, 8:30am UTC](https://hub.mender.io/t/artifact-name-with-script-update-module/1428/3 "2020-01-14T08:30:54Z")
Indeed, it’s not possible to prevent this at the moment. But this is a problem we’re very aware of, and as recently as last week we were discussing potential remedies for this problem. Since no decision has been made yet, I don’t want to promise neither a time nor what form it will take, but rest assured that it’s something we are working to improve. ---
**Author:** ![edocklea](https://avatars.discourse-cdn.com/v4/letter/e/91b2a8/32.png) [@edocklea](https://hub.mender.io/u/edocklea)\ **Post date:** [January 14, 2020, 10:10pm UTC](https://hub.mender.io/t/artifact-name-with-script-update-module/1428/4 "2020-01-14T22:10:34Z")
Sounds good, thanks. In the meantime I am using a custom device inventory attribute to track the firmware version across various updates instead of using the artifact name. ---
**Author:** ![mickael9](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mickael9/32/623_2.png) [@mickael9](https://hub.mender.io/u/mickael9)\ **Post date:** [May 12, 2020, 5:35pm UTC](https://hub.mender.io/t/artifact-name-with-script-update-module/1428/5 "2020-05-12T17:35:40Z")
Hello, do you have any update on this topic? Thanks ---
**Author:** ![kacf](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kacf/32/146_2.png) [@kacf](https://hub.mender.io/u/kacf)\ **Post date:** [May 13, 2020, 11:43am UTC](https://hub.mender.io/t/artifact-name-with-script-update-module/1428/6 "2020-05-13T11:43:53Z")
Yes, we do! The implementation plan for this was just [finished last week](https://tracker.mender.io/browse/MEN-2462). Reading the requirements list might be a little bit technical, but it breaks down to this: - Artifact name will always be updated, as before. - However, in addition, each Update Module will have it’s own namespace, with its own name. For example you will have - `rootfs-image.name: My-rootfs-image-name` - `single-file.name: My-single-file-update` - In addition you can have custom names, like: - `MyCustomApp.name: MyApp-version-2.1` The important thing is that each namespace does not affect the other namespaces, so you can install a new single-file update, and the rootfs-image.name will not change. There are more customizations and details, but that’s the heart of it. ---
**Author:** ![ngrilly](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/ngrilly/32/468_2.png) [@ngrilly](https://hub.mender.io/u/ngrilly)\ **Post date:** [July 22, 2020, 9:38pm UTC](https://hub.mender.io/t/artifact-name-with-script-update-module/1428/7 "2020-07-22T21:38:51Z")
Any update? In the meantime, how do you suggest to track the OS version (and the application version if we use a different artifact type for it)? ---
**Author:** ![kacf](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kacf/32/146_2.png) [@kacf](https://hub.mender.io/u/kacf)\ **Post date:** [July 23, 2020, 6:54am UTC](https://hub.mender.io/t/artifact-name-with-script-update-module/1428/8 "2020-07-23T06:54:01Z")
No update, unfortunately. Still on the roadmap, but development hasn’t started yet. As a workaround, I suggest you put an identifier for your OS and application in a file which gets deployed to the device together with the artifact, and then use an [inventory script](https://docs.mender.io/hosted/client-configuration/inventory) to report that back to the server. ---
**Author:** ![ngrilly](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/ngrilly/32/468_2.png) [@ngrilly](https://hub.mender.io/u/ngrilly)\ **Post date:** [July 23, 2020, 11:14am UTC](https://hub.mender.io/t/artifact-name-with-script-update-module/1428/9 "2020-07-23T11:14:48Z")
Makes sense. Thanks a lot.