# How force value of property to be accept as string for integer value

**URL:** <https://forum.inductiveautomation.com/t/how-force-value-of-property-to-be-accept-as-string-for-integer-value/30465>\
**Category:** Ignition Early Access\
**Created:** [December 5, 2019, 11:02am UTC](https://forum.inductiveautomation.com/t/how-force-value-of-property-to-be-accept-as-string-for-integer-value/30465 "2019-12-05T11:02:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nader.chinichian](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nader.chinichian/32/9261_2.png) [@nader.chinichian](https://forum.inductiveautomation.com/u/nader.chinichian)\
**Post date:** [December 5, 2019, 11:02am UTC](https://forum.inductiveautomation.com/t/how-force-value-of-property-to-be-accept-as-string-for-integer-value/30465/1 "2019-12-05T11:02:53Z")

</div>

Hello  
I want to put some string into the params property of a view. the problem is because property doesn’t have type, if the value is a number the value interpret as number, but I want in some cases it read as string it doesn’t work. putting “” around value add those “” into string itself.  
For example put 123 -\> 123 number  
‘123’ - \> ‘123’ string not 123 string  
I want this: 123 -\> 123 string

---

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [December 5, 2019, 3:23pm UTC](https://forum.inductiveautomation.com/t/how-force-value-of-property-to-be-accept-as-string-for-integer-value/30465/2 "2019-12-05T15:23:01Z")

</div>

You could use a property change script:

```auto
if (previousValue is None) or (currentValue.value != previousValue.value):
	self.custom.key = str(currentValue.value)

```

Two things before you do this:

1. the **value** comparison is important to prevent infinite loops because previousValue and currentValue will always have different timestamps and so will never be equal, whereas their values could be.
2. the check against previousValue being `None` is important because the first time the change event occurs there is no “previous value”.