nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Date Help in PA Flow

Dan Snyder

Hi friends. I have a flow to update staff and faculty relationships and for new staff we want to add a non-constituent organization relationship with their employment information. The connector action to add an organization relationship requires a relation id so I can't use that. What I came up with is adding the information I need for an import to a table in an xlsx file, then creating a csv file in my hosted files so it can be picked up as part of a Queue import. Everything works great, except the date. It is good in the xlsx file, but changes when the CSV file is created and thus the import? Any ideas? Thanks for the help!

827f616f502d4387123e2da2fa065728-huge-im — Xlsx file

eda18ea6a2a15017b809b28aa75d3cc7-huge-im

69d220222aa1f1de1ce0a3b6f56e4846-huge-im

Find more posts tagged with

Microsoft Power Platform

Comments

Alex Wong

@Dan Snyder

Here's 1 solution:

https://powerusers.microsoft.com/t5/Building-Flows/Date-value-is-not-coming-in-date-format-while-creating-csv-from/td-p/1286306

Matt Thacker

Hey @Dan Snyder, use an expression like this

addDays('1899-12-30', int(item()['ORFromDate']), 'dd-MM-yyyy')

Alex Wong

@Alex Wong
But what was the problem with creating the relationship using SKY API?

Dan Snyder

@Matt Thacker and @Alex Wong Thanks for the quick response and pointing me to the expression, that did the trick!

To your question Alex, here is where I have issues adding a non-constituent organization relationship with the connector action. The relation ID being required is the issue that prevents me from being able to add a new non-constituent relationship. It may be that we are not following how BB intends for relationships to behave in RE, but it has been our process so was following that when building this flow. Thanks again for a quick response!

87608cea1c6447f5bf55265cea0bd7d7-huge-im

Ben Regier

@Dan Snyder
Doesn't look like the relation_id is required by the SKY Post Relationship endpoint, so you could do this with HTTP requests if you wanted to keep the process in a flow. Not that there's any need to change it if your import system is working!

Dan Snyder

@Ben Regier Yes, I thought I might try that too even though it was a little outside my comfort zone, but trying it in the endpoint reference page I was not able to get it to work (I didn't try all that hard either). What I did first was just remove the relation id and hit send and received an error (below). Seemed to make sense so I added relation in and still got an error (also below). At that point I felt I was closer with my import process so I moved on ?. If you are able to tell us where I went awry I would love to learn. Thanks!

872103e08c013562e4bb9723e051633c-huge-im

a3f9bf4e4d0a0ba4b9bf6acb59e1bccf-huge-im — Response removing relation_id

1c34a336cb65a6d75cc85ad83967407b-huge-im

419283a5a123822ec4f484e554bf6aba-huge-im

Alex Wong

@Dan Snyder
use the Send HTTP request action and use this endpoint:

This is the request body:

{
"constituent_id": "458424",
"type": "CEO",
"reciprocal_type": "Company",
"relation": {
"type": "Organization",
"name": "New non-constituent org name",
}
}

This will create non-constituent org relationship:

42e380bcb2dc0408ee03ad8c10d14877-huge-im

Alex Wong

@Dan Snyder

Although..re-reading your OP… i'm wondering why you create non-constituent org relationship instead of a constituent org relationship with an actual org record that is your org? (i'm assuming you are putting in new staff's employment information for your org, not all theie previous employment info).

Dan Snyder

@Alex Wong You make a good point and that may be the direction we head in the future, but for now we are just keeping consistent with past practice for a non-con relationship. Not sure there is a good reason for doing it that way other than “it's always been done that way.”

Alex Wong

@Dan Snyder
I hear you, not always easy to change a past decision on how certain things are done.

if you want…try the request body json i sent and see if you want to automate the relationship creation.