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

Announcements

Welcome to the Power Platform Communities
News and Announcements icon
Community site session details

Community site session details

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

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

(0) ShareShare
ReportReport
Posted on by Wouter_K 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:
General topics
  • Verified answer
    v-bacao-msft Profile Picture
    v-bacao-msft Microsoft Employee 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
    Wouter_K 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

News and Announcements

Welcome to the Power Platform Communities

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Mohsin Ali Profile Picture

Mohsin Ali 423

#2
11manish Profile Picture

11manish 308 Super User 2026 Season 2

#3
M Bilal Khan Profile Picture

M Bilal Khan 177

Last 30 days Overall leaderboard

Featured topics

Known issue with browser automation in Power Automate for Desktop on Google Chrome 146 and 147
Share your ideas and struggles with building Power Automate flows!
Survey: Power Automate mobile app
How to Ask for Help with Your Power Automate Workflow
Start and wait for an approval action
Restore a deleted flow
List of actions cheat sheet for Power Automate Desktop
Welcome to the Power Automate forum!

Product updates

Microsoft Power Platform Community release plans