[
https://issues.apache.org/jira/browse/NIFI-14181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18123865#comment-18123865
]
ASF subversion and git services commented on NIFI-14181:
--------------------------------------------------------
Commit 798809a04082d29639645f5d098c7afa036691a2 in nifi's branch
refs/heads/main from Nanjesh Ramesh
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=798809a0408 ]
NIFI-14181 Allow FlowFile attributes in QuerySalesforceObject sObject Name and
Field Names (#11756)
QuerySalesforceObject accepts an optional input FlowFile and already evaluates
Custom WHERE Condition against it, but the sObject Name and Field Names
properties were declared with ENVIRONMENT expression language scope and
evaluated without a FlowFile. A value such as ${object} therefore resolved to an
empty string, and the describe call to Salesforce failed with NOT_FOUND.
Declare both properties with FLOWFILE_ATTRIBUTES scope and evaluate them against
the input FlowFile. Without an input FlowFile the behavior is unchanged.
Because the sObject can now differ between FlowFiles, store the Age Field
timestamp per sObject (last_age_filter.<sObject name, lower case>) instead of as
one value, so incremental queries work with a dynamic sObject Name. The age
field name must exist on every queried object. State written by earlier
versions under last_age_filter is used once as the starting point for the first
sObject queried and is then replaced by the per sObject key.
Also evaluate expression language in Age Delay, which was read without
evaluation.
Add tests for attribute based sObject Name and Field Names, for age filters
kept separate per sObject, and for the migration of the previous state.
> QuerySalesforceObject processor not accepting attributes for sObject Name
> property
> ----------------------------------------------------------------------------------
>
> Key: NIFI-14181
> URL: https://issues.apache.org/jira/browse/NIFI-14181
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 2.1.0
> Reporter: alexduta
> Priority: Minor
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When trying to use QuerySalesforceObject processor with the Property Based
> Query with an attribute defined for the sObject Name property, is giving the
> error
> [\{"errorCode":"NOT_FOUND","message":"The requested resource does not exist"}]
> In my case, I have an attribute called object which value is Account.
> When trying to define sObject Name property as ${object} is throwing the
> above error.
> I need to mention that each time I am using Account as a word in the property
> name, no problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
