Named Objects

Support/help with CloverETL (4.9) and CloverDX (5.0 or newer) implementation problems

Posts: 29
Joined: Wed Sep 02, 2009 12:23 am

Named Objects

Postby CiscoChi » Fri Oct 09, 2009 12:10 am

I'm seeing a lot of inconsistent use of object names. For example, I'm not able to use a relative name for a connection object so creating them from external links becomes an adventure of how to create connections in specific orders for different projects, so I can reference them as Connection0, Connection1, etc. This is a problem across the board for all the objects I've seen: Metadata, Sequences, Lookups, and more(?).

This is fine for small isolated projects, but when we try to use Clover as an infrastructure for all data projects, this becomes high maintenance. Am I missing something?

What is on the horizon to address this?

Posts: 163
Joined: Fri Jul 20, 2007 9:25 am

Re: Named Objects

Postby jurban » Fri Oct 09, 2009 9:36 am

I'm not sure what do you mean by inconsistent object names. You should be able to use project-relative paths to reference external connections, metadata etc. Can you give me an example?

Jaroslav Urban
CloverCARE Support
CloverETL | Rapid Data Integration

Visit us online at