# Updating STRUCTURED Json schema prop is not reflecting in existing translation

**URL:** <https://community.transifex.com/t/updating-structured-json-schema-prop-is-not-reflecting-in-existing-translation/2147>\
**Category:** Q&A\
**Created:** [January 18, 2021, 8:56pm UTC](https://community.transifex.com/t/updating-structured-json-schema-prop-is-not-reflecting-in-existing-translation/2147 "2021-01-18T20:56:07Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![pavan.josyula](https://avatars.discourse-cdn.com/v4/letter/p/f475e1/32.png) [@pavan.josyula](https://community.transifex.com/u/pavan.josyula)\
**Post date:** [January 18, 2021, 8:56pm UTC](https://community.transifex.com/t/updating-structured-json-schema-prop-is-not-reflecting-in-existing-translation/2147/1 "2021-01-18T20:56:07Z")

</div>

Hi, I am facing a weird issue.  
I am using STRCUTRUED Json Schema for my project. I have started with two properties  
{  
“key1”:{  
“string”:“Sample”,  
“context”:“This is simple context”  
},  
“key2”:{  
“string”:“Sample”,  
“context”:“This is simple context”  
}  
}

I have onboarded translators and every thing is working fine.

Now I have recently introduced another property in my source language json file called “character\_limit”

{  
“key1”:{  
“string”:“Sample”,  
“context”:“This is simple context”,  
“character\_limit”:20  
},  
“key2”:{  
“string”:“Sample”,  
“context”:“This is simple context”,  
“character\_limit”:20  
}  
}

But this is not reflecting on the portal page where translators can translate text. I still see the Character Limit is set to 0 no limits are being applied But If I add a brand new resource file from the scratch then it takes the latest schema.

How do I make an update with out dropping existing Translations.

Thanks  
Pavan

---

<div class="post-metadata">

**Author:** ![pavan.josyula](https://avatars.discourse-cdn.com/v4/letter/p/f475e1/32.png) [@pavan.josyula](https://community.transifex.com/u/pavan.josyula)\
**Post date:** [January 19, 2021, 7:29pm UTC](https://community.transifex.com/t/updating-structured-json-schema-prop-is-not-reflecting-in-existing-translation/2147/2 "2021-01-19T19:29:55Z")

</div>

@nina @Panagiotis_Kavrakis Can you please shed some light on how to work with this one

---

<div class="post-metadata">

**Author:** ![Panagiotis\_Kavrakis](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.transifex.com/panagiotis_kavrakis/32/1402_2.png) [@Panagiotis\_Kavrakis](https://community.transifex.com/u/Panagiotis_Kavrakis)\
**Post date:** [January 21, 2021, 11:12am UTC](https://community.transifex.com/t/updating-structured-json-schema-prop-is-not-reflecting-in-existing-translation/2147/3 "2021-01-21T11:12:56Z")

</div>

Hello @pavan.josyula

Thank you for reaching out to our Community.

Let me present to you my investigation according to your issue, and please let me know if I did something different than your scenario.  
I uploaded a Key-Value JSON sample file in a test project of mine using the Key-Value JSON parser. What was actually happened was to have the following image in my application

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/transifex/original/2X/6/61cb0ca846c35d9c92b03bf1b261b52c7371c107.png)

Then I updated the same file adding the tag character\_limit:20 as in your example. Below is the updated part in my file.  
 ![image](https://canada1.discourse-cdn.com/flex030/uploads/transifex/original/2X/5/553e540b3b8d7b94ff8d686bd1710d59cb711cc3.png)  
What was the final result after the update? Nothing different than the first image in my reply.

Moreover, I uploaded the same file with the character\_limit as a new source file, and as you can see either this time my file recognized the character\_limit:20. below is the image of the same file as a new source file.

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/transifex/original/2X/e/ef76646a25289cd57b3d9f823c5576e494d8af3e.png)

So, could you please confirm if the previous actions apply to your issue’s description?

Thank you in advance for your response.

---

<div class="post-metadata">

**Author:** ![pavan.josyula](https://avatars.discourse-cdn.com/v4/letter/p/f475e1/32.png) [@pavan.josyula](https://community.transifex.com/u/pavan.josyula)\
**Post date:** [January 21, 2021, 7:36pm UTC](https://community.transifex.com/t/updating-structured-json-schema-prop-is-not-reflecting-in-existing-translation/2147/4 "2021-01-21T19:36:47Z")

</div>

> [@Panagiotis\_Kavrakis](#):
>
> I uploaded a Key-Value JSON sample file in a test

Yes, this is what I see @Panagiotis_Kavrakis.  
To make character\_limit effective i would either need to delete all the existing translations and update the source language file or add as new resource.

Thanks  
Pavan

---

<div class="post-metadata">

**Author:** ![Panagiotis\_Kavrakis](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.transifex.com/panagiotis_kavrakis/32/1402_2.png) [@Panagiotis\_Kavrakis](https://community.transifex.com/u/Panagiotis_Kavrakis)\
**Post date:** [January 25, 2021, 11:18am UTC](https://community.transifex.com/t/updating-structured-json-schema-prop-is-not-reflecting-in-existing-translation/2147/5 "2021-01-25T11:18:41Z")

</div>

Hello @pavan.josyula

Thank you for your confirmation.

Since I couldn’t reproduce your issue to make character\_limit effective, could you please share your initial file and the second version of your file, in order to investigate further your issue?

Kind regards,  
Panagiotis

---

<div class="post-metadata">

**Author:** ![pavan.josyula](https://avatars.discourse-cdn.com/v4/letter/p/f475e1/32.png) [@pavan.josyula](https://community.transifex.com/u/pavan.josyula)\
**Post date:** [January 27, 2021, 8:47pm UTC](https://community.transifex.com/t/updating-structured-json-schema-prop-is-not-reflecting-in-existing-translation/2147/6 "2021-01-27T20:47:05Z")

</div>

@Panagiotis_Kavrakis

**Original Json**  
{  
“A”: {  
“O”: {  
“string”: “Basket approved by approver”,  
“context”: “Basket approved by approver” ,  
“developer\_comment”:“This is my test developer comment”  
},  
“P”: {  
“string”: “Payment approved by approver”,  
“context”: “Payment approved by approver”  
}  
},  
“D”: {  
“O”: {  
“string”: “Basket declined by approver”,  
“context”: “Basket declined by approver”  
},  
“P”: {  
“string”: “Payment declined by approver”,  
“context”: “Payment declined by approver”  
}  
},  
“E”: {  
“O”: {  
“string”: “Approval timeout escalation actioned”,  
“context”: “Approval timeout escalation actioned”  
},  
“P”: {  
“string”: “Approval timeout escalation actioned”,  
“context”: “Approval timeout escalation actioned”  
}  
},  
“L”: {  
“O”: {  
“string”: “Basket locked for editing”,  
“context”: “Basket locked for editing”  
}  
},  
“M”: {  
“O”: {  
“string”: “Basket modified by approver”,  
“context”: “Basket modified by approver”  
}  
},  
“O”: {  
“O”: {  
“string”: “Order created from approved basket”,  
“context”: “Order created from approved basket”  
}  
},  
“R”: {  
“O”: {  
“string”: “Approval reminder actioned”,  
“context”: “Approval reminder actioned”  
},  
“P”: {  
“string”: “Approval reminder actioned”,  
“context”: “Approval reminder actioned”  
}  
},  
“S”: {  
“O”: {  
“string”: “Basket submitted for approval”,  
“context”: “Basket submitted for approval”  
},  
“P”: {  
“string”: “Payment submitted for approval”,  
“context”: “Payment submitted for approval”  
}  
},  
“U”: {  
“O”: {  
“string”: “Basket unlocked”,  
“context”: “Basket unlocked”  
}  
}  
}

JSON with Char limit  
{  
“A”: {  
“O”: {  
“string”: “Basket approved by approver”,  
“context”: “Basket approved by approver”,  
“character\_limit”:50,  
“developer\_comment”:“This is my test developer comment”  
},  
“P”: {  
“string”: “Payment approved by approver”,  
“context”: “Payment approved by approver”,  
“character\_limit”:50  
}  
},  
“D”: {  
“O”: {  
“string”: “Basket declined by approver”,  
“context”: “Basket declined by approver”,  
“character\_limit”:50  
},  
“P”: {  
“string”: “Payment declined by approver”,  
“context”: “Payment declined by approver”,  
“character\_limit”:50  
}  
},  
“E”: {  
“O”: {  
“string”: “Approval timeout escalation actioned”,  
“context”: “Approval timeout escalation actioned”,  
“character\_limit”:50  
},  
“P”: {  
“string”: “Approval timeout escalation actioned”,  
“context”: “Approval timeout escalation actioned”,  
“character\_limit”:50  
}  
},  
“L”: {  
“O”: {  
“string”: “Basket locked for editing”,  
“context”: “Basket locked for editing”,  
“character\_limit”:50  
}  
},  
“M”: {  
“O”: {  
“string”: “Basket modified by approver”,  
“context”: “Basket modified by approver”,  
“character\_limit”:50  
}  
},  
“O”: {  
“O”: {  
“string”: “Order created from approved basket”,  
“context”: “Order created from approved basket”,  
“character\_limit”:50  
}  
},  
“R”: {  
“O”: {  
“string”: “Approval reminder actioned”,  
“context”: “Approval reminder actioned”,  
“character\_limit”:50  
},  
“P”: {  
“string”: “Approval reminder actioned”,  
“context”: “Approval reminder actioned”,  
“character\_limit”:50  
}  
},  
“S”: {  
“O”: {  
“string”: “Basket submitted for approval”,  
“context”: “Basket submitted for approval”,  
“character\_limit”:50  
},  
“P”: {  
“string”: “Payment submitted for approval”,  
“context”: “Payment submitted for approval”,  
“character\_limit”:50  
}  
},  
“U”: {  
“O”: {  
“string”: “Basket unlocked”,  
“context”: “Basket unlocked”,  
“character\_limit”:50  
}  
}  
}

Please find the attachments![Add Resource With Original\_en|690x466]

(upload://d5gGbZIeY5i9HYFzfgskiS8vYRy.png) ![Afterupdating_Source_WithCharlimit_json](https://canada1.discourse-cdn.com/flex030/uploads/transifex/original/2X/1/191d40bd0c12032bea3af9866ada04f8856ba8e0.png) ![No Charlimit is set](https://canada1.discourse-cdn.com/flex030/uploads/transifex/original/2X/8/8eb117af6c25fec28957da1e7caf22c73f7cfc22.png)

 ![Update Source with Character Limit](https://canada1.discourse-cdn.com/flex030/uploads/transifex/original/2X/2/2c2b192d6ee34b3234f453b2a5a094306b8263cb.png) ![Add Resource With Original_en](https://canada1.discourse-cdn.com/flex030/uploads/transifex/original/2X/5/5bb4bd16dc3d3a3e53fee86c8f9adc6371300a30.png)

---

<div class="post-metadata">

**Author:** ![Panagiotis\_Kavrakis](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.transifex.com/panagiotis_kavrakis/32/1402_2.png) [@Panagiotis\_Kavrakis](https://community.transifex.com/u/Panagiotis_Kavrakis)\
**Post date:** [January 29, 2021, 10:52am UTC](https://community.transifex.com/t/updating-structured-json-schema-prop-is-not-reflecting-in-existing-translation/2147/7 "2021-01-29T10:52:29Z")

</div>

Hello @pavan.josyula ,

Thank you for sharing your files.  
Indeed I reproduced your issue, and I have forwarded it to our development team. Once I have an update I will let you know.

In the meantime, you could enable the TM-auto fillup in order when you upload the resource as a new file the translations will be completed from the previous resource automatically.

Thank you in advance for your patience and cooperation.

Kind regards,  
Panagiotis

---

<div class="post-metadata">

**Author:** ![pavan.josyula](https://avatars.discourse-cdn.com/v4/letter/p/f475e1/32.png) [@pavan.josyula](https://community.transifex.com/u/pavan.josyula)\
**Post date:** [February 2, 2021, 9:56pm UTC](https://community.transifex.com/t/updating-structured-json-schema-prop-is-not-reflecting-in-existing-translation/2147/8 "2021-02-02T21:56:24Z")

</div>

> [@Panagiotis\_Kavrakis](#):
>
> you could enable the TM-auto fillup in order when

Thank you I will check that option

---

<div class="post-metadata">

**Author:** ![Panagiotis\_Kavrakis](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.transifex.com/panagiotis_kavrakis/32/1402_2.png) [@Panagiotis\_Kavrakis](https://community.transifex.com/u/Panagiotis_Kavrakis)\
**Post date:** [March 18, 2021, 9:34am UTC](https://community.transifex.com/t/updating-structured-json-schema-prop-is-not-reflecting-in-existing-translation/2147/9 "2021-03-18T09:34:27Z")

</div>

Hello @pavan.josyula ,

I hope you are well and fine.  
I would like to inform you that the issue with the character limit has been resolved.

Feel free to share your feedback with us.

Have a nice day!

Kind regards,  
Panagiotis