Not being to upload Custom Variables as a part of CM offline conversion data about megalista HOT 7 CLOSED

Hi Sandhya.

First of all, sorry for the delay in getting back to you.

Can you confirm when this instance of Megalista was deployed on your client environment?

It would be really helpful to know the Megalista "version" they're running so that we can pinpoint the issue.

For your reference, we've merged the commit that implemented custom variables in Megalista on Aug 16, 2021, so if you've deployed Megalista for this client earlier, high chances that they're just using an old version.

If not, let us know and we can try to debug it together.

Cheers,
Caio

from megalista.

Hi Sandhya.

First of all, sorry for the delay in getting back to you.

Can you confirm when this instance of Megalista was deployed on your client environment?

It would be really helpful to know the Megalista "version" they're running so that we can pinpoint the issue.

For your reference, we've merged the commit that implemented custom variables in Megalista on Aug 16, 2021, so if you've deployed Megalista for this client earlier, high chances that they're just using an old version.

If not, let us know and we can try to debug it together.

Cheers, Caio

Hi Caio,

Thank you so much for your response. I really appreciate it and no worries about the delay part.

Regarding the "Megalista version", I did a redeploy with the latest version around a month and a half back, as the previous version deployed was "Megalist".
Also, I went through pull request #41, it seems the code running in the client's env is updated with the same.

Kindly let me know how to move forward with this. Also, happy to provide more details if needed.

Thanks,
Sandhya

from megalista.

Thanks for confirming Sandhya!

This is kind of surprising because we do have tests verifying that the customVariables are built into the final CM API body for the CM connector (see here for your reference).

Can you provide an anonymized/mock sample of the data you're trying to upload so that I can try to reproduce the issue on my side? Maybe there's some specific structure that you're trying to use that we have not predict in our tests.

from megalista.

Thanks for confirming Sandhya!

This is kind of surprising because we do have tests verifying that the customVariables are built into the final CM API body for the CM connector (see here for your reference).

Can you provide an anonymized/mock sample of the data you're trying to upload so that I can try to reproduce the issue on my side? Maybe there's some specific structure that you're trying to use that we have not predict in our tests.

Thanks again for your quick response Caio! Really appreciate it.

Please find here a screenshot of the sample data for your reference.

In the above screenshot, Variables U1, U3, and U7 stand for ConfCode, OAB_ID, and Device ID, respectively. I hope this helps.
Kindly let me know f I can help with anything else.

from megalista.

Hi @caiotomazelli,

I hope the sample data that I shared earlier has been of help. But was just curious to know if there are any updates related to the same. Additionally, happy to help with any further data/information or support.

Thanks,
Sandhya

from megalista.

Hi @Sandhya-1988 sorry for the delay getting back to you.

Looks like it's going to be an easy fix: your custom variable columns are using snake_case as opposed to camelCase, which is what we expect, as you can see below:

Also, check out our Example BQ Data for Testing to see how data should be structured in BQ for customVariables (it must be a single Array column).

I'll close the issue for now but feel free to reopen if you need anything else.

Cheers,
Caio

from megalista.

Hi @Sandhya-1988 sorry for the delay getting back to you.

Looks like it's going to be an easy fix: your custom variable columns are using snake_case as opposed to camelCase, which is what we expect, as you can see below:

Also, check out our Example BQ Data for Testing to see how data should be structured in BQ for customVariables (it must be a single Array column).

I'll close the issue for now but feel free to reopen if you need anything else.

Cheers, Caio

Thank you so much for the inputs @caiotomazelli . We implemented them and it worked finally.
So happy to see the results.

Really appreciate all your help and valuable time on this. Thanks again.

from megalista.