web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / GUID gets converted to...
Power Automate
Unanswered

GUID gets converted tot ‘Something’ while inserting into SQL.

(0) ShareShare
ReportReport
Posted on by 67

Hi fellow Flow fans,

 

Something strange. See Picture.

 

  • Getting a record from Dynamics when records get changed / created. (using CDS connector)
  • Then inserting some of the fields in SQL (al varchar(50)
  • All goes well EXCEPT for the RecordID = GUID (AL_entity_id) – in this case opportunity. This somehow gets converted to some strange value.

Flow_converts_GUID_to_something.png

 

See results in SQL. Even stranger the column AL_User is also a GUID in the source system, this does not get incorrectly converted.

 

 

Flow_converts_-_SQL_table.png

 

 

By the way: Got a workaround by adding a Space (“ ”&)  in front of the OpportunityID. Somehow the the GUID gets inserted correctly in that way.

 

Kind Regards,

 

Wouter Kessener

 happy flowing 🙂

Categories:
I have the same question (0)
  • Verified answer
    v-bacao-msft Profile Picture
    on at

    Hi @Wouter_K ,

     

    I did a test on my side, the field type in SQL table is also varchar (50), but the Opportunities id is still the original format.

    You could try to use Compose to store the record id and then insert the output of compose into the SQL table.

    23.PNG

    From your screenshot, it seems that the RecordID is transcoded into base64. You could also try to decode it first using decodeBase64() function.

    Expression reference:

    decodeBase64(triggerBody()?['crba2_opportunitiesid'])

    Image reference:

    24.PNG

    Hope it helps.

     

    Best Regards,

  • Wouter_K Profile Picture
    67 on at

    Thanks so much for taking the time te respond.

     

    Your sugested solutions (decode or compose)  are also a good workarrounds.  But still a workarround in my opinion. I find it stange that the GUID (AL_User) does not seem to need an compose or decode step to get the actuel GUID value to SQL.

     

    Anyway. Thans again. I will surely mark your response as a solution.

     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 538 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 405 Moderator

#3
abm abm Profile Picture

abm abm 252 Most Valuable Professional

Last 30 days Overall leaderboard