Dataloader.io vs TIBCO Cloud Integration (including BusinessWorks and Scribe)

• Extracting Salesforce attachments in original file format! I do not know of a tool that can do this better, or more efficiently! This is a huge benefit to companies that would like to extract attachments from Salesforce for tasks like data migrations.
• Cross-object data extract within one file. You can pull data from related objects as long as there is a populated lookup from the object you are extracting, to another object (Child or Parent).
• UI is simple and requires very little to no training. Given the acquisition of Mulesoft by Salesforce, I would not be surprised if DataLoader.IO is rolled out as the new global data loading tool for Salesforce.

Read full review

• Scribe can dependably map or sync data between systems. When you have different systems being used by many departments, this is the tool to keep the data in-sync!
• API's are widely used by many applications and companies. Tibco Cloud Integration allows companies to integrate data from an older ERP system with a newer system using an API.
• Tibco provides the flexibility for business users, developers and anyone in-between to understand where data is moving within their organization.
• One example of flexibility of the solution is easily manipulating data on the fly.

Read full review

• At the moment, I can't find a way to rename jobs. This would be useful to organize what was previously created hastily by techs in a rush.
• A preview of the job, especially upserts, would take a great deal of stress away from some of us (especially those who are not so confident in their ETL practice).
• A native vlookup equivalent may be a welcome addition.

Read full review

• Missing functionality: We like to run all the files available in the FTP when clicking the run button. Right now, we have to click the run button several times (or have multiple solutions) in order to run files from our FTP site one at a time.
• Generating column fields every time a file changes from the source in the FTP is very tedious. Working in integrations makes me have to go back and forth a lot of the time, and doing this is incredibly annoying.
• The security is horrendous. We installed an on-premise agent on the customer side, but we don't want them even touching the ETL tool at all. The only knowledge we are fine with knowing and being able to see is that they installed the agent, not the solutions themselves.
• Our company's connector would have to point to the dataset name rather than dataset ID. It was very frustrating because we change the dataset name a lot, and then we'd have to repoint it.
• It's very difficult to monitor the different integrations that go on because there isn't a consolidated dashboard.

Read full review

• HUGE time saving. When we need to clean or review data, we used to have to do it line by line. This can do the work within excel and make cleanup/management an afternoons work as opposed to a week.
• Rollback what you did/change/deleted is relatively simple if you remember to back up the data you are manipulating.

Read full review

• The data migration has been extremely slow. Things that should have taken a short amount of time have gone way past where any of us though.
• Job monitoring has been more resource intensive and time consuming that planned for.
• Researching and searching for things is time consuming.
• There is no way to easily organize solutions. So there are hundreds of solutions in the list with no easy way to put them in folders or something like that. The only thing you can do is name them specifically so that you can filter them. But filtering is not very good in Scribe.
• The concept of Scribe is good. I like the graphical flow builds in the maps. It just doesn't work very well yet. maybe as they improve it.

Read full review