1. Home
  2. Integration Platform as a Service (iPaaS) Software
  3. TIBCO Integration (including BusinessWorks and Flogo) Reviews
  4. User Review of TIBCO Integration (including BusinessWorks and Flogo)
Scribe Replication Service Issues
Updated November 02, 2020

Scribe Replication Service Issues

Anonymous | TrustRadius Reviewer
Score 3 out of 10
Vetted Review
Verified User

Overall Satisfaction with TIBCO Cloud Integration (including BusinessWorks and Scribe)

Scribe Replication Service (RS) is used only by me to replicate 73 MS CRM 365 entities to an Azure SQL Database, used as a "data warehouse". The 73 tables in our Azure SQL database are updated by the RS every night. The intent was to have a copy of the most useful CRM entities in the cloud for reporting purposes with Power BI.
  • Daily Replication succeeds without errors more often than not.
  • The Replication Service does not include the ability to "pre-filter" the data in any way, i.e., it gets ALL records from the beginning of time and ALL columns, many of which are not used in CRM.
  • Several errors with records that fail to be processed are frequently reported, including "Execution timeout expired", "data would be truncated", and "Cannot insert duplicate key row". I've opened support cases for these, but none seem to have a solution I can use.
  • The row counts of all entities replicated should be approximately equal to the row counts in the source database, but several entities' counts are significantly different.
  • In the Scribe Online web app pages, the error details panel cannot be resized andruns off the bottom of the screen, making impossible to read the entire error message.
  • Positive - It has allowed me to create a "data warehouse" in the cloud for reporting purposes.
  • Negative - Its lack of stability and reliability has caused me to spend time investigating errors.
  • Negative - The subscription price.
I have not evaluated other products like TIBCO.
  • Self-taught
With the limitations of Scribe RS, I don't think training had any impact.
Scribe Replication has enabled me to load data from a Microsoft Dynamics CRM data source into an Azure SQL Database, which our organization uses as a data source for Power BI reports.

Do you think TIBCO Integration (including BusinessWorks and Flogo) delivers good value for the price?

Not sure

Are you happy with TIBCO Integration (including BusinessWorks and Flogo)'s feature set?

No

Did TIBCO Integration (including BusinessWorks and Flogo) live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of TIBCO Integration (including BusinessWorks and Flogo) go as expected?

Yes

Would you buy TIBCO Integration (including BusinessWorks and Flogo) again?

Yes

Some issues I encountered with Scribe Replication related to replication job failures do not have a solution, but can be ignored, according to support personnel. This occasionally requires me to manually check whether specific data has been successfully replicated. On some cases I've opened with support, the solution provided assumed I was using the Scribe CRM Integration solution instead of the Replication solution.
Most of the time, the CRM to Azure SQL Database Replication solution works correctly without user intervention.
Scribe Replication Service is not well-suited for maintaining accurate copies of database tables. It also has very limited connection options for source and target.

TIBCO Integration (including BusinessWorks and Flogo) Feature Ratings

Cloud Data Integration
3.0
Pre-built connectors
3
Monitoring console
3

Evaluating TIBCO Cloud Integration (including BusinessWorks and Scribe) and Competitors

Purchasing

The decision was made by a 3rd party consultant.
I would evaluate other products.

Infrastructure Environment

We don't use Integration, only Scribe Replication Service.
We don't use Integration, only Scribe Replication Service.

Learnings and Advice

We only use Scribe Replication to transfer MS CRM data to an Azure SQL Database which is used as a data source for Power Bi Reports.
If using Scribe Replication to transfer MS CRM data to an Azure SQL Database, be prepared to occasionally investigate replication failures, modify source data, or delete all data for a CRM entity from the target database and restart its replication from the beginning.
Very little; it seems that most customers use Scribe Integration rather than Replication.
Create a SQL script that will compare for each entity the count of target records replicated to that of the source records. Run this periodically to check the synchronization.

Create a job to actually delete the target records marked as 'Deleted'.
If it was my decision, I would take time to locate and evaluate alternative products.

Using TIBCO Cloud Integration core features

We only use Scribe Replication to transfer MS CRM data to an Azure SQL Database which is used as a data source for Power Bi Reports.
We only use Scribe Replication to transfer MS CRM data to an Azure SQL Database which is used as a data source for Power Bi Reports.
I have not evaluated other competitors.

Using TIBCO Cloud Integration (including BusinessWorks and Scribe)

1 - Database Administrators
  • None, due to limitations of Replication Services
It has already replicated over 26 GB of CRM data to our Azure SQL Database (our "data warehouse").
The Azure SQL Database is currently the data source for dozens of Power BI reports we have published.
We don't have resources to locate and evaluate alternate products.

TIBCO Cloud Integration (including BusinessWorks and Scribe) Implementation

  • Third-party professional services
I can't remember.
Change management was minimal - None
  • The limitations of Scribe Replication I discovered.