[
https://issues.jboss.org/browse/TEIIDDES-2684?page=com.atlassian.jira.plu...
]
Steven Hawkins commented on TEIIDDES-2684:
------------------------------------------
It looks like there are multiple issues that are being discussed here. I don't think
there is a scenario here where the runtime resolving logic is different. Whether imported
through the Designer or Teiid, Salesforce will always have a Campaign table.
The original issue is that the Designer importer logic for is not out of synch with Teiid
- which incorporates TEIID-3112 and other changes. So there will be queries that execute
correctly using a dynamic vdb, that result in a source error (not a resolving error) with
a Designer VDB.
The error "Group does not exist: SalesForceSource.Campaign AS Campaign"
doesn't match the debug plan. Is that from a different user query?
SalesForce importer issue
-------------------------
Key: TEIIDDES-2684
URL:
https://issues.jboss.org/browse/TEIIDDES-2684
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export, Patch Release
Affects Versions: 9.0.4
Environment: MAC OS
Reporter: Matus Makovy
Assignee: Mark Drilling
Fix For: 10.0.1, 9.2.1
Attachments: salesdynamic-vdb.xml, TEIIDDES_2684.log
According to conversation in TEIID-3112 this is a Designer issue. If I understood
correctly, it has been fixed in Teiid and now the changes have to be made in TD SF
importer.
I have a VDB with Source model that is created via SalesForce importer and I am getting
this error:
{quote}
Didn't understand relationship 'Opportunitys' in FROM part of query call. If
you are attempting to use a custom relationship, be sure to append the '__r' after
the custom relationship name. Please reference your WSDL or the describe call for the
appropriate names
{quote}
when trying to submit this query:
{quote}
select distinct YEAR("Opportunity"."CloseDate") as
"Opportunity_CloseDate1" from "SalesForceSource".Campaign AS
"Campaign" LEFT OUTER JOIN "SalesForceSource".Opportunity AS
"Opportunity" ON Campaign."Id" = Opportunity."CampaignId"
order by YEAR("Opportunity"."CloseDate") ASC LIMIT 0 , 32
{quote}
It works without problems with dynamic VDB.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)