# Multiply dataset columns with number

**URL:** <https://forum.inductiveautomation.com/t/multiply-dataset-columns-with-number/74258>\
**Category:** Ignition\
**Created:** [May 29, 2023, 12:00pm UTC](https://forum.inductiveautomation.com/t/multiply-dataset-columns-with-number/74258 "2023-05-29T12:00:37Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [May 30, 2023, 3:42pm UTC](https://forum.inductiveautomation.com/t/multiply-dataset-columns-with-number/74258/8 "2023-05-30T15:42:50Z")

</div>

Also doable with `system.dataset.map` from my [Ignition Extensions](https://forum.inductiveautomation.com/t/ignition-extensions-convenience-utilities-for-advanced-users/64615) module.

Or you could get fancy and use a custom tag history aggregate:  
[https://docs.inductiveautomation.com/display/DOC81/Custom+Tag+History+Aggregates](https://docs.inductiveautomation.com/display/DOC81/Custom+Tag+History+Aggregates)

It would probably be _best_ to fix this data at the source, though. If these tag values should be 3x higher...why not enable tag scaling on the root tag, so you don't have to manually adjust history down the road?

---

_[View the full topic](https://forum.inductiveautomation.com/t/multiply-dataset-columns-with-number/74258)._