Pdot-metadata

[karmic seal]

Hello - Unfortunately there's no way around this. You can always split the information into two parts (sine the 500 character limit is for each value in a key/value pair)

[unkempt cloak]

I don't follow, what do you mean split in two parts? This is how we're currently sending addtional license/ticket purchases

{
"region": {
"value": "Brazil",
"id": "4"
},
"buyerFullName": "ACMA Junk",
"buyerEmail": "[e-mail]",
"additionalCertificationsLicenses": [
{
"1": [
{
"fullName": "asdf",
"email": "[e-mail]",
"productId": {
"value": "Brazil",
"id": "4"
}
},
{
"fullName": "asd",
"email": "[e-mail]",
"productId": {
"value": "Brazil",
"id": "4"
}
}
]
},
{
"2": [
{
"fullName": "asdfasdf",
"email": "[e-mail]",
"productId": 2
},
{
"fullName": "parth2",
"email": "[e-mail]",
"productId": 2
}
]
}
]
}

[karmic seal]

Let's back up - can you show me an example request that failed because you hit metadata limits?

[unkempt cloak]

yes. give me a sec I'll grab the full request

is it easier for you to check via request id?

req_kLyk78CfYZ6SOq

[karmic seal]

yup, that's perfect - let me take a look!

[unkempt cloak]

its the purchaseObj in the metadata that exceeds the limit of 500. Not sure if I can divide that up somehow

[karmic seal]

purchaseObj is also a hash just a hash with a lot of key/value pairs - you could store each of these as separate keys under metadata - like you can set 'purchaseObj[region]' as a key and the value as '{"value": "Asia", "id": 7}'

I need to head out but if you need more help @slender meteor can answer your questions

[unkempt cloak]

got it, yeah I removed most of those outside the hash. But I still run into the issue if a user purchases upto 10 licenses. Since I need the name and email of those 10 people via one key / value pair @slender meteor

any other light you can shed on this @slender meteor ?

[slender meteor]

I don't think there's a good workaround aside from what karbi mentioned already. Ideally you would cache this on your end in a database for reference, otherwise you will have to break them up into multiple separate key/value pairs