data translating ampersands but it shouldn't

  • 22Views
  • Last Post 1 weeks ago
0
votes
Alvin Mah posted this 3 weeks ago

I'm exposing a sql view to be rendered in ODATA that refers to a hyperlink

as example

https://cloud.goacoustic.com/campaign-automation/Email/Scheduled_and_sent?emails=scheduled-and-sent&id=23437907&type=SENT

but when rendered by the odata API is comes out incorrect

https://cloud.goacoustic.com/campaign-automation/Email/Scheduled_and_sent?emails=scheduled-and-sent&id=23437907&type=SENT

According to documentation I should be able to use single quotes to prevent extra interpretation but it doesn't work.  Any suggestions?

 

 

Order By: Standard | Newest | Votes
0
votes
Dmitriy Muzurov posted this 3 weeks ago

Hello Alvin,

Thank you for submitting a ticket with us.

Let us know if we understood the scenario correctly: an SQL view from SQL Server is used for OData endpoint, the data in this view in the form of URI is migrated and ampersands are formatted on their way to the target.

If it's correct, please let us know the name of the target, so that we reproduce the issue on our side.

We are looking forward to hearing from you.

0
votes
Alvin Mah posted this 3 weeks ago

That is a correct understanding.  Here is the endpoint with example

SAMIDW2

https://connect.skyvia.com/4055j60j/vSFDCCustomerEmailHistories(1)/

You'll notice for the MailingContentField characters "&" are replaced with "&" Looking like

https://cloud.goacoustic.com/campaign-automation/Email/Scheduled_and_sent?emails=scheduled-and-sent&id=22609045&type=SENT

instead of

https://cloud.goacoustic.com/campaign-automation/Email/Scheduled_and_sent?emails=scheduled-and-sent&id=22609045&type=SENT

 

0
votes
Alvin Mah posted this 3 weeks ago

hey just a status update.  I was able to create a new odata v4 endpoint (SAMIDW3) pointing to the same db connection.  It looks like v4 formats correctly and odata v2 (SAMIDW2) does not.  So my issue is solved for now but you may want to fix odata v2 for other customers.

0
votes
Dmitriy Muzurov posted this 2 weeks ago

Dear Alvin,

We are glad to know your issue is resolved.

It is still not clear what target you used in your scenario.

Let us know the target your endpoint was connected to and migrated the data to.

We are looking forward to hearing from you.

0
votes
Alvin Mah posted this 2 weeks ago

The target is an azure synapse database (SAMIDW2) which created a view which produced the right URL.  OData v2 seems to be the issue.  All I did to fix my issue was abandon the Odatav2 endpoint and create a brand new Odata v4 which pointed to the same azure synapse database.

The purpose was to serve up to be consumed by a SFDC instance but that is irrelevant.  Just comparing the two endpoints the MailingContent field is rendered differently even though they are pointing to the same record.

https://connect.skyvia.com/4055j60j/vSFDCCustomerEmailHistories(1)/

https://connect.skyvia.com/4v6pzl72/vSFDCCustomerEmailHistories(1)/

 

0
votes
Dmitriy Muzurov posted this 1 weeks ago

Dear Alvid,

Please provide us with DDL scripts both for source and target databases, so that we reproduce the issue on our side.

We are looking forward to hearing from you.

Close