Skip to main content
  • EN

Hello everyone,

I am back and I have 99% of this very important workbench completed (thanks to you all for helping with last question).

My next "issue" is stumping me.

My workbench is reading form SDE and writing to a GDB.

One of the features I have is a Cutout object and within the SDE is the Cutout_tb (Sde table object) which carries the Child records of the Parent Cutout.

I simply bring it in and connect it to feature merger to get the attribute I want (fuse size).

Seems simple enough but the Workbench wont read records from the table in the workbench whether I put it in its own reader or not. Its puzzling because if I make separate workbench and simply write to access database it reads and writes the records fine.

Is there any way to get the workbench to get the child records straight from SDE upon reading the cutout object (such as reading the SDE Relationship Class object in SDE)? Or is there a way to get the simpler way of simply having the table read in workbench and join it to cutouts?

It is very simple issue and Im very puzzled why its not working.

Thanks in advance for any assistance you may provide.

Savas Giarenakis

Eversource

Hello @sav426,

 

 

I have a couple of questions to ensure I am understanding your workflow regarding reading the child records of the parent table.

 

 

1) What do you mean when you refer to a Cutout Object? Are you referring to a view(thus a sample of the original table)?

 

2) Currently, my thought process is you have two tables(Parent1 and Child1). The Child1 Table contains the Child records of the Parent1 table. With a Relationship class joining them. Currently, if you read in the Parent table, you do no receive the records from the Child table. Is that correct?

 

 

3) What type of Relationship class is joining the two features? Simple or Composite? Attributed or Non-Attributed?

 

1-1, 1-M, or M-N?

Hello @sav426,

 

 

I have a couple of questions to ensure I am understanding your workflow regarding reading the child records of the parent table.

 

 

1) What do you mean when you refer to a Cutout Object? Are you referring to a view(thus a sample of the original table)?

 

2) Currently, my thought process is you have two tables(Parent1 and Child1). The Child1 Table contains the Child records of the Parent1 table. With a Relationship class joining them. Currently, if you read in the Parent table, you do no receive the records from the Child table. Is that correct?

 

 

3) What type of Relationship class is joining the two features? Simple or Composite? Attributed or Non-Attributed?

 

1-1, 1-M, or M-N?
hi there.

 

 

A cutout is an electrical device aka as a fuse. It is a point object and the parent record. Its also its own feature in the SDE named ELECTRIC.CUTOUT

 

 

The cutout Table is the child record and is a sde table object within the SDE.

 

 

It is a 1 to many join (1 parent to multi children)

 

 

Within the SDE is a relationclass between these two objects.

 

 

Can that be duplicated within FME? If not then I pull out the Table and use feature merger to join the objects.

 

 

The table was NOT reading yesterday but is today and I believe that to not be an FME issue but a network issue here.

 

 

To sum it up:

 

 

Can relationship classed between parent and child be made at point of reading the feature instead of having to bring in the tables and use the featuremerger transformer?

 

 

Thanks!

 

 

Hello @sav426,

 

 

I have a couple of questions to ensure I am understanding your workflow regarding reading the child records of the parent table.

 

 

1) What do you mean when you refer to a Cutout Object? Are you referring to a view(thus a sample of the original table)?

 

2) Currently, my thought process is you have two tables(Parent1 and Child1). The Child1 Table contains the Child records of the Parent1 table. With a Relationship class joining them. Currently, if you read in the Parent table, you do no receive the records from the Child table. Is that correct?

 

 

3) What type of Relationship class is joining the two features? Simple or Composite? Attributed or Non-Attributed?

 

1-1, 1-M, or M-N?
Hi Trent Ive figured out my problem.

 

 

How do I get the TABLE records to read BEFORE anything else?

 

 

That seems to be the issue.

 

 

Hi Trent Ive figured out my problem.

 

 

How do I get the TABLE records to read BEFORE anything else?

 

 

That seems to be the issue.

 

 

Hi @sav426

 

 

If you have two separate readers, you can toggle the reader(that contains the feature type you wish to read first) to the top of the Navigator pane, so it should be the first reader in the Navigator. Alternatively, if you have only 1 reader, with multiple feature types I believe you can move the feature type to the top of the canvas(so that is is the first feature vertically).

 

 

Let me know if that helps.

Reply


Community Stats

29,712
Posts
112,921
Replies
37,368
Members
Terms & ConditionsCookie settings