[JBoss JIRA] (TEIIDDES-2447) Failed to import SalesForce Metadata
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2447?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2447:
----------------------------------------
Please log a separate issue with Modeshape Teiid Sequencer so it can properly check for single quotes and handle them properly.
I'll work this as a bug to better handle the error in Designer.
> Failed to import SalesForce Metadata
> ------------------------------------
>
> Key: TEIIDDES-2447
> URL: https://issues.jboss.org/browse/TEIIDDES-2447
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Priority: Critical
> Attachments: sfddl (1).ddl
>
>
> Using the Teiid Connection import, the attached DDL has been retrived from salesforce instance. However Designer fails to import it, and gives NO clue as to what is wrong.
> 1) The DDL should be successfully imported
> 2) When there is something wrong that Designer does not understand it needs to give a meaningful error, as per the location of the file and context
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (TEIIDDES-2447) Failed to import SalesForce Metadata
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2447?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-2447:
----------------------------------------
Not two groups of single quotes. If a single quote is in the text then it is escaped with another quote.
> Failed to import SalesForce Metadata
> ------------------------------------
>
> Key: TEIIDDES-2447
> URL: https://issues.jboss.org/browse/TEIIDDES-2447
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Priority: Critical
> Attachments: sfddl (1).ddl
>
>
> Using the Teiid Connection import, the attached DDL has been retrived from salesforce instance. However Designer fails to import it, and gives NO clue as to what is wrong.
> 1) The DDL should be successfully imported
> 2) When there is something wrong that Designer does not understand it needs to give a meaningful error, as per the location of the file and context
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (TEIIDDES-2447) Failed to import SalesForce Metadata
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2447?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-2447 at 3/9/15 3:36 PM:
----------------------------------------------------------------
I see potentially both UI and runtime issues here:
1) Teiid dialect may not be auto-selecting in the DDL importer (UI)
2) On error, the importer should high-light the offending DDL text (UI)
- I verified this by using the straight DDL Import wizard with Teiid dialect option.
3) The parser appeared to have an issue with the Pick List.
- Typical pick list is a comma separated list wrapped by single quotes: i.e. ( 'AZ, MN, MO, MD, KY' )
- The pick list in question had the following content which had 2 groups of quoted values rather than 1. So I may be the SF translator returning invalid data?
{code}
'0.00 Amount not approved,Backdate Subsc Start-date,Billing/Shipping Info Missing,Billing Account Number Invalid,
Billing Acct/Info Incorrect/Missing,Billing Address Incorrect,Billing Address Missing,Contract Incorrect/Missing/Unsigned,
Contract Missing/Not Signed,Contract Numbers Incorrect,Contract Numbers Missing,Co-Terms Info Incorrect/Missing,
Credit Card Declined,Credit Related/Payment Terms Issues,Credit Status/Payment Terms Issues,
Customer Hold or Delivery Delay,Cut-Off Time Exceeded,Description Missing,Discount Not Approved,
Duplicate Order,EU Login Incorrect/Missing,Finance Approval Required,Handwritten Change Not Acceptable,
Incorrect Account Classification,Incorrect SKUs,Invalid RH Entitlement Login,Legal/BD Review & Approval,
Legal Agreement not attached / Missing,Legal Approval,Legal Approval Required,Legal Entity Not Correct,
Login/Acct # Invalid/Missing,Missing Pages,Missing Reference to Existing Agreement,Missing Signatures,
Missing SKUs,New Party / Account Request,No PO Letter needs Approval,No PO Letter Required,Other,
Payment Terms Missing,Payment Terms Not Approved,PO/Credit Card Info Incorrect/Missing,PO Missing,
PO not attached / missing,Pricing Incorrect,Product/Discount Approval Required,Qty/Price/Products Not Equal,
Renewal Dates are Incorrect/Missing,Renewal Info/Start Date Needed,Renewal Information Incorrect/Missing,
Sales Mgmt or PM Approval Required,Shipping Address Incorrect,Shipping Address Missing,
Shipping Info Incorrect/Missing,SKU/Qty/Currency/Price Incorrect,SKU Qty/Price/Desc Issue,Start/End Date Missing,
Start Date Over 14 Days Old,Subsc Dates/Term Issue,Tax Info Missing/Incorrect,Unclear - Auto entitlement Vs Keys,
VAT # Missing/Incorrect,VAT number missing/incorrect,Waiting Saba # or CM# or Others' ' Info,Wrong Billing Acct#,Wrong Currency'
{code}
was (Author: blafond):
I see potentially both UI and runtime issues here:
1) Teiid dialect may not be auto-selecting in the DDL importer (UI)
2) On error, the importer should high-light the offending DDL text (UI)
- I verified this by using the straight DDL Import wizard with Teiid dialect option.
3) The parser appeared to have an issue with the Pick List.
- Typical pick list is a comma separated list wrapped by single quotes: i.e. ( 'AZ, MN, MO, MD, KY' )
- The pick list in question had the following content which had 2 groups of quoted values rather than 1
{code}
'0.00 Amount not approved,Backdate Subsc Start-date,Billing/Shipping Info Missing,Billing Account Number Invalid,
Billing Acct/Info Incorrect/Missing,Billing Address Incorrect,Billing Address Missing,Contract Incorrect/Missing/Unsigned,
Contract Missing/Not Signed,Contract Numbers Incorrect,Contract Numbers Missing,Co-Terms Info Incorrect/Missing,
Credit Card Declined,Credit Related/Payment Terms Issues,Credit Status/Payment Terms Issues,
Customer Hold or Delivery Delay,Cut-Off Time Exceeded,Description Missing,Discount Not Approved,
Duplicate Order,EU Login Incorrect/Missing,Finance Approval Required,Handwritten Change Not Acceptable,
Incorrect Account Classification,Incorrect SKUs,Invalid RH Entitlement Login,Legal/BD Review & Approval,
Legal Agreement not attached / Missing,Legal Approval,Legal Approval Required,Legal Entity Not Correct,
Login/Acct # Invalid/Missing,Missing Pages,Missing Reference to Existing Agreement,Missing Signatures,
Missing SKUs,New Party / Account Request,No PO Letter needs Approval,No PO Letter Required,Other,
Payment Terms Missing,Payment Terms Not Approved,PO/Credit Card Info Incorrect/Missing,PO Missing,
PO not attached / missing,Pricing Incorrect,Product/Discount Approval Required,Qty/Price/Products Not Equal,
Renewal Dates are Incorrect/Missing,Renewal Info/Start Date Needed,Renewal Information Incorrect/Missing,
Sales Mgmt or PM Approval Required,Shipping Address Incorrect,Shipping Address Missing,
Shipping Info Incorrect/Missing,SKU/Qty/Currency/Price Incorrect,SKU Qty/Price/Desc Issue,Start/End Date Missing,
Start Date Over 14 Days Old,Subsc Dates/Term Issue,Tax Info Missing/Incorrect,Unclear - Auto entitlement Vs Keys,
VAT # Missing/Incorrect,VAT number missing/incorrect,Waiting Saba # or CM# or Others' ' Info,Wrong Billing Acct#,Wrong Currency'
{code}
> Failed to import SalesForce Metadata
> ------------------------------------
>
> Key: TEIIDDES-2447
> URL: https://issues.jboss.org/browse/TEIIDDES-2447
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Priority: Critical
> Attachments: sfddl (1).ddl
>
>
> Using the Teiid Connection import, the attached DDL has been retrived from salesforce instance. However Designer fails to import it, and gives NO clue as to what is wrong.
> 1) The DDL should be successfully imported
> 2) When there is something wrong that Designer does not understand it needs to give a meaningful error, as per the location of the file and context
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (TEIIDDES-2447) Failed to import SalesForce Metadata
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2447?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2447:
----------------------------------------
I see potentially both UI and runtime issues here:
1) Teiid dialect may not be auto-selecting in the DDL importer (UI)
2) On error, the importer should high-light the offending DDL text (UI)
- I verified this by using the straight DDL Import wizard with Teiid dialect option.
3) The parser appeared to have an issue with the Pick List.
- Typical pick list is a comma separated list wrapped by single quotes: i.e. ( 'AZ, MN, MO, MD, KY' )
- The pick list in question had the following content which had 2 groups of quoted values rather than 1
{code}
'0.00 Amount not approved,Backdate Subsc Start-date,Billing/Shipping Info Missing,Billing Account Number Invalid,
Billing Acct/Info Incorrect/Missing,Billing Address Incorrect,Billing Address Missing,Contract Incorrect/Missing/Unsigned,
Contract Missing/Not Signed,Contract Numbers Incorrect,Contract Numbers Missing,Co-Terms Info Incorrect/Missing,
Credit Card Declined,Credit Related/Payment Terms Issues,Credit Status/Payment Terms Issues,
Customer Hold or Delivery Delay,Cut-Off Time Exceeded,Description Missing,Discount Not Approved,
Duplicate Order,EU Login Incorrect/Missing,Finance Approval Required,Handwritten Change Not Acceptable,
Incorrect Account Classification,Incorrect SKUs,Invalid RH Entitlement Login,Legal/BD Review & Approval,
Legal Agreement not attached / Missing,Legal Approval,Legal Approval Required,Legal Entity Not Correct,
Login/Acct # Invalid/Missing,Missing Pages,Missing Reference to Existing Agreement,Missing Signatures,
Missing SKUs,New Party / Account Request,No PO Letter needs Approval,No PO Letter Required,Other,
Payment Terms Missing,Payment Terms Not Approved,PO/Credit Card Info Incorrect/Missing,PO Missing,
PO not attached / missing,Pricing Incorrect,Product/Discount Approval Required,Qty/Price/Products Not Equal,
Renewal Dates are Incorrect/Missing,Renewal Info/Start Date Needed,Renewal Information Incorrect/Missing,
Sales Mgmt or PM Approval Required,Shipping Address Incorrect,Shipping Address Missing,
Shipping Info Incorrect/Missing,SKU/Qty/Currency/Price Incorrect,SKU Qty/Price/Desc Issue,Start/End Date Missing,
Start Date Over 14 Days Old,Subsc Dates/Term Issue,Tax Info Missing/Incorrect,Unclear - Auto entitlement Vs Keys,
VAT # Missing/Incorrect,VAT number missing/incorrect,Waiting Saba # or CM# or Others' ' Info,Wrong Billing Acct#,Wrong Currency'
{code}
> Failed to import SalesForce Metadata
> ------------------------------------
>
> Key: TEIIDDES-2447
> URL: https://issues.jboss.org/browse/TEIIDDES-2447
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Priority: Critical
> Attachments: sfddl (1).ddl
>
>
> Using the Teiid Connection import, the attached DDL has been retrived from salesforce instance. However Designer fails to import it, and gives NO clue as to what is wrong.
> 1) The DDL should be successfully imported
> 2) When there is something wrong that Designer does not understand it needs to give a meaningful error, as per the location of the file and context
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (TEIIDDES-2447) Failed to import SalesForce Metadata
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2447?page=com.atlassian.jira.plu... ]
Van Halbert reassigned TEIIDDES-2447:
-------------------------------------
Assignee: Van Halbert
> Failed to import SalesForce Metadata
> ------------------------------------
>
> Key: TEIIDDES-2447
> URL: https://issues.jboss.org/browse/TEIIDDES-2447
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Ramesh Reddy
> Assignee: Van Halbert
> Priority: Critical
> Attachments: sfddl (1).ddl
>
>
> Using the Teiid Connection import, the attached DDL has been retrived from salesforce instance. However Designer fails to import it, and gives NO clue as to what is wrong.
> 1) The DDL should be successfully imported
> 2) When there is something wrong that Designer does not understand it needs to give a meaningful error, as per the location of the file and context
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (TEIIDDES-2447) Failed to import SalesForce Metadata
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2447?page=com.atlassian.jira.plu... ]
Van Halbert reassigned TEIIDDES-2447:
-------------------------------------
Assignee: Barry LaFond (was: Van Halbert)
> Failed to import SalesForce Metadata
> ------------------------------------
>
> Key: TEIIDDES-2447
> URL: https://issues.jboss.org/browse/TEIIDDES-2447
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Priority: Critical
> Attachments: sfddl (1).ddl
>
>
> Using the Teiid Connection import, the attached DDL has been retrived from salesforce instance. However Designer fails to import it, and gives NO clue as to what is wrong.
> 1) The DDL should be successfully imported
> 2) When there is something wrong that Designer does not understand it needs to give a meaningful error, as per the location of the file and context
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (TEIIDDES-2447) Failed to import SalesForce Metadata
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2447?page=com.atlassian.jira.plu... ]
Van Halbert commented on TEIIDDES-2447:
---------------------------------------
If you leave the dialect option to be auto-select, don't see any parsed sql statements. But get 2 error messages:
1 instances of DDL statement of type [ddl:ddlProblem] were found, but cannot be processed
1024 instances of a DDL statement of type [dd:unknownStatement] were found, but cannot be processed
However, if I change the dialect to be Teiid. Then I get the Import DDL page, with the following message top:
No difference operations were found
See the import messages for more info.
But I look in the .log file, no messages.
> Failed to import SalesForce Metadata
> ------------------------------------
>
> Key: TEIIDDES-2447
> URL: https://issues.jboss.org/browse/TEIIDDES-2447
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Ramesh Reddy
> Priority: Critical
> Attachments: sfddl (1).ddl
>
>
> Using the Teiid Connection import, the attached DDL has been retrived from salesforce instance. However Designer fails to import it, and gives NO clue as to what is wrong.
> 1) The DDL should be successfully imported
> 2) When there is something wrong that Designer does not understand it needs to give a meaningful error, as per the location of the file and context
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (TEIIDDES-2447) Failed to import SalesForce Metadata
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIIDDES-2447:
--------------------------------------
Summary: Failed to import SalesForce Metadata
Key: TEIIDDES-2447
URL: https://issues.jboss.org/browse/TEIIDDES-2447
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Reporter: Ramesh Reddy
Priority: Critical
Using the Teiid Connection import, the attached DDL has been retrived from salesforce instance. However Designer fails to import it, and gives NO clue as to what is wrong.
1) The DDL should be successfully imported
2) When there is something wrong that Designer does not understand it needs to give a meaningful error, as per the location of the file and context
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (TEIIDDES-2446) Transformation editor fails to open
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIIDDES-2446:
--------------------------------------
Summary: Transformation editor fails to open
Key: TEIIDDES-2446
URL: https://issues.jboss.org/browse/TEIIDDES-2446
Project: Teiid Designer
Issue Type: Bug
Components: Editors
Reporter: Ramesh Reddy
Priority: Critical
Transformation editor fails to open when Designer is set to connect with later versions of the Teiid.
1) it should work with later versions Teiid
2) It should always should be able to open the transformation editor
The below is the exception in the .log file
!ENTRY org.teiid.designer.transformation 4 0 2015-03-09 09:57:40.875
!MESSAGE java.lang.Exception: No ExecutionAdmin factory registered for teiid instance version 8.10.0.
!STACK 0
java.lang.RuntimeException: java.lang.Exception: No ExecutionAdmin factory registered for teiid instance version 8.10.0.
at org.teiid.designer.core.ModelerCore.getTeiidQueryService(ModelerCore.java:2199)
at org.teiid.designer.transformation.aspects.sql.SqlTransformationMappingRootSqlAspect.parseSQL(SqlTransformationMappingRootSqlAspect.java:522)
at org.teiid.designer.transformation.aspects.sql.SqlTransformationMappingRootSqlAspect.getTransformationInfo(SqlTransformationMappingRootSqlAspect.java:386)
at org.teiid.designer.core.metadata.runtime.RuntimeAdapter.addTransformationWords(RuntimeAdapter.java:412)
at org.teiid.designer.core.metadata.runtime.RuntimeAdapter.addIndexWord(RuntimeAdapter.java:172)
at org.teiid.designer.core.index.ModelIndexer.addIndexWord(ModelIndexer.java:311)
at org.teiid.designer.core.index.ModelIndexer.index(ModelIndexer.java:164)
at org.teiid.designer.core.index.Index.add(Index.java:127)
at org.teiid.designer.core.index.ModelIndexer.indexResource(ModelIndexer.java:240)
at org.teiid.designer.core.builder.VdbModelBuilder.indexResource(VdbModelBuilder.java:265)
at org.teiid.designer.core.builder.VdbModelBuilder.indexResources(VdbModelBuilder.java:290)
at org.teiid.designer.core.builder.VdbModelBuilder.indexResources(VdbModelBuilder.java:281)
at org.teiid.designer.core.builder.VdbModelBuilder.buildResources(VdbModelBuilder.java:125)
at org.teiid.designer.vdb.VdbIndexedEntry.synchronizeIndex(VdbIndexedEntry.java:199)
at org.teiid.designer.vdb.VdbModelEntry.synchronizeModelEntry(VdbModelEntry.java:612)
at org.teiid.designer.vdb.Vdb.addModelEntry(Vdb.java:444)
at org.teiid.designer.vdb.Vdb.addEntry(Vdb.java:358)
at org.teiid.designer.runtime.preview.jobs.CreatePreviewVdbJob.runImpl(CreatePreviewVdbJob.java:170)
at org.teiid.designer.runtime.preview.jobs.WorkspacePreviewVdbJob.runInWorkspace(WorkspacePreviewVdbJob.java:129)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Caused by: java.lang.Exception: No ExecutionAdmin factory registered for teiid instance version 8.10.0.
at org.teiid.designer.runtime.registry.TeiidRuntimeRegistry.getQueryService(TeiidRuntimeRegistry.java:148)
at org.teiid.designer.core.ModelerCore.getTeiidQueryService(ModelerCore.java:2197)
... 20 more
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month