[Portal] Salesforce record-created trigger accepts an object missing required CreatedDate field
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 48/100
- issue の種類
- バグ
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- azure, javascript
調査の方向性
Start by locating the Salesforce trigger setup and object picker in the portal, then trace how the “When a record is created” trigger selects fields for its source query. Reproduce with the ssot__Account__dlm mapping and compare it with the standard Account mapping. Done means setup clearly rejects or explains objects missing CreatedDate, and the object labels distinguish the API names.
索引モデルが issue の本文から書いたものです。
説明
One-line summary
Salesforce “When a record is created” accepts an object that lacks the required CreatedDate field, then fails at runtime; similar object labels make the incompatible selection difficult to recognize.
Area of the portal
Triggers
Severity
Medium (workaround exists, but annoying)
What happened?
With a Connected Salesforce connection, I selected Account in the Salesforce Object Type picker for When a record is created. Setup accepted the selection, but the trigger subsequently showed Failed, with HTTP 400:
Salesforce failed to complete task:
SELECT Id,CreatedDate FROM ssot__Account__dlm
^
ERROR at Row:1:Column:11
No such column 'CreatedDate' on entity 'ssot__Account__dlm'.
Source: Salesforce.Common.
The authenticated connector object picker returned these distinct mappings:
| DisplayName | Name (API name) |
|---|---|
| Account | ssot__Account__dlm |
| Accounts | Account |
The filter displays only Account, so it is not apparent that this is a different object from the standard CRM Account object. The connection remains Connected, but the source query fails before any event is delivered to the destination Azure Function.
This report confirms a failure for ssot__Account__dlm with this trigger; it does not establish that all Data Cloud objects are unsupported.
What did you expect to happen?
- Validate the selected object's required fields during setup and reject incompatible selections with an actionable explanation, rather than accepting setup and failing on the first source query.
- Include API names in the object picker and selected filter, for example Accounts (Account) versus Account (ssot__Account__dlm).
- If validation belongs to the underlying Salesforce connector rather than the portal, surface that validation clearly in the setup flow.
Steps to reproduce
- Use a Connected Salesforce connection whose object picker includes both
Accountandssot__Account__dlm. - Create a When a record is created trigger.
- Select Account (the picker entry whose API name is
ssot__Account__dlm). - Configure a Function App destination and save the trigger. In this case, recurrence was every 5 seconds.
- Observe the trigger transition to Failed, with a query error stating that
CreatedDatedoes not exist onssot__Account__dlm.
Creating a test record is not required to encounter the missing-field query error.
Page URL
App version / build / commit SHA
0dbbbf83
Browser & version (User-Agent)
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/157.0.0.0 Safari/537.36 Edg/157.0.0.0
Viewport size & theme
1499x777 @ dark
Anything else
The standard CRM object appears as Accounts with API name Account. Selecting that object is the proposed workaround for monitoring normal CRM accounts; successful end-to-end delivery after changing the selection has not yet been verified.
- 主要言語
- JavaScript
- スター
- 20
- フォーク
- 7
- PR マージ指標
- 30日以内にマージされた PR はありません
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
Azure/Connectors のほかの issue
-
bug portal
難易度 2/5 1〜3時間 初心者へのやさしさ 67/100
Azure/Connectors#178 ·
-
bug portal
難易度 3/5 1〜2日 初心者へのやさしさ 58/100
Azure/Connectors#179 ·
-
難易度 4/5 3〜5日 初心者へのやさしさ 54/100
Azure/Connectors#176 ·
-
bug portal
難易度 4/5 3〜5日 初心者へのやさしさ 43/100
Azure/Connectors#175 ·
-
難易度 3/5 1〜2日 初心者へのやさしさ 62/100
Azure/Connectors#174 ·
Azure/Connectors の issue をすべて見る
似ている issue
-
对信息编解码工具建议オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 64/100
-
難易度 2/5 1〜3時間 初心者へのやさしさ 79/100
メンテナーはふだん 1 日以内に返信
-
good first issue tests
難易度 1/5 1〜3時間 初心者へのやさしさ 68/100
メンテナーはふだん 1 日以内に返信
-
bug role: dev-lead
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
briangwalker/TrussExplorer#424 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 80/100
eliasstravik/herdr-projects#1032 ·