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; } } }

ArcGIS for Power Automate - v2023.3 - 変更履歴と更新情報（2023年9月18日）

AnthonyLatini

ArcGIS Connectors for Power Automate は、新機能、速度と使いやすさの向上、およびバグ修正を提供するために定期的に更新されています。2023.3 のアップデートは品質リリースです。以下の機能に対してパフォーマンスの改善、新しいアクション、およびバグ修正が行われました。 <\/P>

このリリースは2023年9月18日から展開を開始します。すべての地域への配信には最大48時間かかる場合があります（政府レベルのサイトでは最大2週間かかる場合があります）。 <\/EM><\/P>変更が表示されない場合は、キャッシュをクリアし、Webブラウザーを再起動してPower Automateで変更を確認してください。<\/P>いつものように、ご意見やご相談があればお知らせください。<\/P> <\/P>---<\/P>ArcGIS Enterprise<\/FONT><\/P>今年のサンディエゴで開催されたユーザー会議に参加された方は、Power Automate内でのArcGIS Enterpriseサポートについてチームが言及していたのを聞いたかもしれません。ついにそれが実現しました！ArcGIS Enterpriseコネクターを段階的に展開しています。<\/P>最初のフェーズは現在Power Automateで利用可能で、ArcGISコネクターにあるすべてのCRUDベースの操作が含まれています。例えば、ArcGISコネクターと同様にフィーチャーレイヤー内のレコードや添付ファイルの追加、削除、更新を開始できます。 <\/P><\/span><\/P>ArcGIS Enterpriseコネクターの第2フェーズには、ジオコーディング、ジオエンリッチメント、およびネットワーキングに関連する残りのアクションが含まれます。また、ArcGIS Enterprise 11.2以降向けのWebhookサポートも追加作業中です。現在のフェーズでは、フィーチャーレイヤー上でWebhookを手動で設定する必要があります。<\/P>その方法の詳細はこちらをご覧ください。<\/P>注意：これはプレビューアクションであり、WebhookサポートはArcGIS Enterprise 11.2のリリースまで完全には統合されません。 <\/EM><\/P>次のトピックに移る前に、ArcGIS Enterpriseコネクターについていくつか注意点があります。 <\/P>要件<\/STRONG><\/U>: <\/P>- ArcGIS EnterpriseコネクターはArcGIS Enterprise 11.0以上をサポートしています<\/P>- Webhookプレビューを使用するにはArcGIS Enterprise 11.1以上が必要です<\/P>- エンタープライズインスタンスはインターネット（または少なくともPower Automate自体）へのアクセスが必要です。ファイアウォール内や切断環境ではコネクターは動作しません。 <\/P>セットアップ情報はすべて当社のドキュメントでご確認いただけます。 <\/P>ドキュメント<\/STRONG>: ArcGIS Enterpriseコネクターのセットアップ023 ArcGIS for Microsoft 365 | ドキュメント<\/A><\/P>

<\/P>

Find Address Candidates<\/FONT><\/P>さまざまなフローや皆様からのフィードバックを通じて共通して求められていたのは、ジオコーディングアクションでカスタムジオコーダーを使用できる機能でした。具体的にはFind Address Candidate<\/EM>とGeocode Addresses<\/EM>です。デフォルトではこれら2つのアクションは

ArcGIS World Geocoding Service <\/A>からトップマッチのみを返し、その値を他のアクションやアプリケーションに渡せます。<\/P>
動的にはトップ結果のみ返します。例えば「15 Maple Street」をジオコードすると、フロー完了後に最良マッチが返されます。この時、通り名以外の情報は意図的に渡していません。ちなみにこれは米国で最も
 一般的な住所の一つです。

結果ではWorld Geocoderがイングランドの位置を返しました。また返されたスコアも100ではなく（完全一致ではないことを意味します）。 <\/P><\/span><\/P> <\/P>次に同じ変数を新しいアクションFind Address Candidates. このアクションで最初に異なる点はジオコーダーを変更できることです。このリストは動的にあなたのArcGIS Online（および将来的にはEnterprise）組織から取得されます。この例では引き続きArcGIS World Geocoding Serviceを使用します。<\/P><\/span><\/P>同じ住所を使うと結果画面が少し異なります。この結果では今度はTop candidate でソートされています。 <\/P><\/span><\/P> <\/P>生データ出力を見ると、この住所には複数結果があることがわかります。 <\/P> $\AnthonyLatini_5-1694822354104.png\$

このアクションからは、トップ候補またはスコア80以上で結果をフィルタリングするフローを作成して渡すことができます。このアクションを試してみて、組織内カスタムジオコーダーとの新たな可能性を広げてください。

$\AnthonyLatini_0-1694822711523.png\$

$\AnthonyLatini_1-1694822717567.png\$

Token Expiration / Manual Sign In

Power Automate用ArcGIS Connectorsで大きな課題だったワークフローは、トークン期限切れ時に手動で接続を更新することでした。例えば組織でログインタイムアウトが14日間の場合、フローを継続するためには資格情報を手動で更新する必要がありました。しかしこれはもう不要となり、2023年5月初旬から実装されています。

内部テストでは90日間トークンタイムアウトでも同じ資格情報でフロー実行すればトークンが自動更新され、手動サインイン不要と確認済みです。

Attachment Support

この機能は以前からコネクターにありますが、本投稿でも強調したいと思います。

Power Automate用ArcGIS Connectorsで添付ファイル使用サポート追加

Attachment Triggers

添付ファイル作成時
添付ファイル削除時
添付ファイル更新時

$\AnthonyLatini_0-1695087519105.png\$ アクション - EsriJSONへのエクスポートが正しい値を返さない<\/LI>Fetch updatesおよびchangesアクションに関連するバグを修正 - Fetch updatesは選択されたFeature Layerに結果をフィルタリングしない<\/LI>フィーチャーレイヤーのCRUD操作に関連するバグを修正 - 設定で「Add」のみが有効な場合、レコードの作成に失敗する<\/LI> Fetch updates, changes, and deletions <\/EM>が結果の本文で予期しない変更を返していた問題を修正<\/LI>特定のレイヤーでトリガーが失敗する問題を修正<\/LI>長いフローでランタイムの不整合に関連する問題を修正<\/LI>空のジオメトリを含むフローが完了しない問題を修正<\/LI>レコードの更新時に「number」が必要だが「string」になっている問題を修正<\/LI>適切なクエリパラメータがあってもクエリがレコードを返さない問題を修正<\/LI> Create a feature layer <\/EM>でArcGIS Onlineに追加されたレイヤーのデータフィールドが結合される稀な問題を修正<\/LI><\/UL>UI\/UXの改善<\/FONT><\/STRONG><\/U><\/H3>GeoenrichmentアクションのRing Buffersで透かしテキストが表示されなかった問題を修正<\/LI><\/UL> <\/P>生活の質向上アップデート<\/FONT><\/STRONG><\/U><\/P>ユーザーはフィーチャーレイヤーで利用可能な編集オプションを選択できるようになりました。以前は編集には追加、削除、更新すべてにチェックが必要でした。<\/LI>複数のエラーメッセージを人間に読みやすい形式に更新<\/LI>トークンの有効期限はユーザーの組織によって管理され、リフレッシュトークンは手動で更新する必要がありません<\/LI><\/UL>---<\/P>Power Automate用ArcGIS Connectorsコネクタは引き続き成長と拡大を続けています。次の数ヶ月でArcGIS Enterpriseサポートの次フェーズを展開予定です。また、皆様からのフィードバックをまとめ、新しい helper actions <\/EM>や自動化を楽しく刺激的にする方法に取り組んでいます。<\/P>いつも通り、コネクタについて（良い点でも悪い点でも）皆様のご意見やフィードバックをお聞かせください。Power AutomateとArcGIS Connectorを組織内でどのように使っているか理解することが私たちの活力源です。自動化をあなたのグループの日常ルーチンの一部にしましょう！ <\/P> <\/P>

タグ付けされた投稿をもっと見る

TLongSUGF

@AnthonyLatini

Can you confirm "The ArcGIS Enterprise connector supports ArcGIS Enterprise 11.0 and above"

I am currently using Enterprise 10.9.1 and am able to run get data from feature layer successfully.

AnthonyLatini

@TL2 - While different instances of ArcGIS Enterprise may work (meaning anything below ArcGIS Enterprise 11.0), we only officially support ArcGIS Enterprise 11.0 and above.

acarmody

Can this ArcGIS Enterprise workflow be made available for the ArcGIS Online connector in the next update?

It is limiting that the connector controls the webhook - there doesn't seem to be a way to edit it in power automate? and it can't be modfied on the feature layer (except renaming). I've tested changing the 'change type' to wildcard (*) - the power automate flow ceases to hear any feature changes.

If I'm completely wrong about this please disregard and please could you share a how-to?

Many thanks.

SeanKMcGinnis

Hi @acarmody - the ability to create a flow by manually creating webhook following a similar pattern with ArcGIS Online is possible, but is not a direct product capability. The flow creation is less of a configurable component and more of a technical experience which goes against the intent for a no code/low code process builder.

The reason we are handling webhooks in the post you reference is due to differences in the way ArcGIS Online & ArcGIS Enterprise have implemented webhooks. The intent is to create a more consistent experience, modeled after the ArcGIS Connector, with the 11.2 release of ArcGIS Enterprise.

It makes sense that the flow would become unresponsive if you changed the 'change type' to a wildcard would fail. The action has no concept of how to handle an asterisk. Could you please provide a little detail on what you are trying to accomplish by listening for all webhook types?

Maybe submit it as an idea for consideration in future releases.

acarmody

Hi @SeanKMcGinnis , thank you!

Our organisation has AGOL layers that need to be watched for any/all changes. I'm rebuilding our Integromat webhooks in Power Automate. Hoping to keep using 'wildcard' so only one flow is needed for each layer.

erica_poisson

Hi @AnthonyLatini @SeanKMcGinnis -

Can I get some confirmation here on token life - above it seems to be saying 90 days, which I thought was the case for GCC. I'm having some issues with my flows using the ArcGIS connector failing due to authentication issues well before their 90 days is up.

Can you please share any insights here?

Thank you,

Erica

TLongSUGF

@erica_poisson

I have a simple flow for both ArcGIS and Survey123 connectors, it runs every hour and alerts me if the connection failed. I don't trust the token life either.

erica_poisson

@TL2 - could you share a screen capture of this flow? I'd be very interested in setting something similar up. This continues to be a massive pain point of using this technology. I have reminders all over the place to check tokens, but it seems like the length keeps changing!

TLongSUGF

Note, it "fails" every time but I make the Terminate to run if it fails and log Successful. If it's actually successful, it sends the email.

SeanKMcGinnis

@erica_poisson & @TL2 - thank you for the comments and sharing the way you are working with the token situation.

There are two tokens that we are managing within the ArcGIS Connectors for Power Automate. The first is the session token which is what authenticates the user in the flow and is updated each time the flow runs. The second token is the refresh token, which manages the connection settings validating whether the user can make a request back to Online or Enterprise to get a session token. The expiration of this token is managed buy your Organization and by default is set to 14 days, but is configurable.

Each time a flow runs we update refresh token, which in turn starts the clock to timing out against your Organization or Enterprise. If the flow has not run within the duration of your refresh token timeout, it will fail. The way I have been getting around this is I have a scheduled flow for each of my connections that runs on a daily basis to query against a specific feature layer. This forces the refresh token to be refreshed before it times out, preventing me from getting unexpected connection issues.

I hope this helps and am open to any feedback or questions.

SeanKMcGinnis

@TL2 - that is the Survey123 connector which uses a different authentication pattern than the ArcGIS Connectors for Power Automate and timeout every two weeks. The ArcGIS for Microsoft 365 team is working with the Survey123 team to update their authentication pattern to more closely follow our pattern.

erica_poisson

@SeanKMcGinnis I think the community would greatly benefit from some sort of blog to walk them thru how to set up what you've described above. I certainly know I would need some step-by-step guidance to configure such a flow.

erica_poisson

@SeanKMcGinnis -

I recently went thru the work of clearing out all of my duplicate connections for ArcGIS and Survey123 in Power Automate. I created two new connections and rebuilt all of my flows to ensure that my Connections list was clean and I stopped having so many issues with flows failing and needing to be fixed. This has worked great until today.

I got an error from one of my flows that uses the Survey123 Create report action. The failure was for a missing token. When I go into Power Automate > Connections, I see that my Survey123 Connection shows a Status = Connected.

I know that if I go into the broken flow and click the ... on the top corner of the Create report action, that I can use +Add new connection to fix the flow, however I also know this adds a duplicative Survey123 connection to my list of available Connections which is annoying/not ideal/difficult to manage.

Do you have any suggested strategies for dealing with this situation? My Organization has ArcGIS Online and I am not able to find a way to increase token length thru Organization settings.

I've posted about this as a question in both the Power Automate and Survey123 communities in the hopes of a quick response. Any help or advice on dealing with this would be amazing. The Create report action could be great, but this is incredibly frustrating and makes it unreliable and not really a tool worth using because of it.

Question posted in Power Automate community here.

Thank you,

SeanKMcGinnis

Hi @erica_poisson,

Unfortunately, the Survey123 connector is still using the older pattern of authentication. Our team is working with the Survey123 team to update the authentication pattern to the one currently in use by the ArcGIS Connectors for Power Automate. I do not have an estimate time when this will be completed, but when deployed (and promoted to GCC), it will address the timeout issue.

As updating the connection so you no longer have duplicates, I go to the Survey123 Connection and click the 'Switch Account' button and re-enter my credentials. This renews the authentication tokens and prevents creating another connection.

Switch Account process will allow you to reauthenticate the connection and keep all Flows running.

daveostrander

Hello @SeanKMcGinnis

I am trying to understand the rules regarding tokens for our current connection. Unfortunately, we are still at 10.9.1 for our ArcGIS Enterprise and will likely need to be at that version for some time. However, I did create a custom connecter using the Esri technical article that works well with Survey123 and ArcGIS Enterprise Portal (I know it's not supported exactly). I am just now getting back to testing/working with this connection, and if memory serves correctly, I have had flows where the token expired on my trigger (no longer showing dynamic content and listing the item ID instead of the survey name), but it still functioned when surveys were submitted. So my question is a multi-fold one: will a custom ArcGIS Enterprise connector connection expire (if so, how long before that happens), and within my flow, can the trigger expire and continue to function? Also, you mentioned a workaround to keep connections alive.

You stated:

"If the flow has not run within the duration of your refresh token timeout, it will fail. The way I have been getting around this is I have a scheduled flow for each of my connections that runs daily to query against a specific feature layer. This forces the refresh token to be refreshed before it times out, preventing me from getting unexpected connection issues."

I built two scheduled flows in an attempt to follow what you were laying out above. I have a scheduled flow with my custom connector connection, which queries all my published surveys. The other scheduled flow makes an HTTP POST request to generate a token, parses the JSON to retrieve the token as dynamic content, and makes an HTTP GET request to query all of my published surveys. That one doesn't work because the token I get doesn't seem to work with the header's Authorization: Bearer <access token> scheme. Assuming both are working, would either of these scheduled flows have the effect of keeping the custom connector alive? And where does one get a Bearer access token if it differs from a portal-generated token? I am just seeking as much clarification as possible since there seem to be different types of tokens and connectors/connections at play. Thank you for any guidance you can provide with this.

daveostrander

Hello @SeanKMcGinnis

Since my last post, I have done some further research into OAuth2. From that, I have come to the understanding that performing the authorization and token requests in a flow will not work to keep my ArcGIS Enterprise custom connector alive because a flow produced in this way would require credentials to be entered manually at the redirect page. Instead, this workflow is really what the custom connector does for me on its own. So, my question now is, will the ArcGIS Enterprise custom connector refresh itself indefinitely (whether or not any flows run), or do I still need to have a recurrence flow that runs daily, which queries the connection using an action type flow? In my case, the flow I set up queries all of my published Survey123 surveys. So far, in my week or two of testing, I haven't seen the custom connector lose connection, requiring a manual sign-in to reauthorize it. However, even losing connection at 90 days would be bad for a production workflow where the public submits surveys at will. Again, thank you for any guidance you can provide on this.

daveostrander

Hello @SeanKMcGinnis

At this point in my testing, the token on my get surveys action query connection has finally expired (elapsing the 20,260-minute mark), and as a result, my recurrence flow fails with a "missing token" error. So, it would seem that setting up a recurrence flow to query the connection to keep it alive doesn't seem to have panned out for me here.

However, my trigger-based flows that run when surveys are submitted using webhooks from the survey123 website still function as expected even though they have also expired (showing the survey item ID instead of the survey name and not displaying dynamic content). This development is promising! So, I think I am only down to one question: Will my custom ArcGIS Enterprise Connector work indefinitely as long as my flows are only trigger-type flows using webhooks? I guess the next test for that won't be for 90 days when the refresh token will max out (if I understand that correctly). I'd prefer not to wait that long to find out, so any guidance you can provide on the expiration of the ArcGIS Enterprise custom connector would be greatly appreciated. Thanks in advance!

会話に参加する

サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか？無料アカウントを登録してください。

クイックリンク

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.