Help Please:Course 'Using DataFlux® Data Management Studio' - receiving errors in Lesson 6 Practices

[User_7455]

Hi All, hoping for a bit of guidance please.

I'm currently completing the 'Using DataFlux® Data Management Studio' course on SAS 9 Data Management Learning Subscription.

In Lesson 6 ACT: Entity Resolution, I'm having trouble with the practice exercise in section 6.2 Creating Match Codes.  I even skipped to the Solutions section and am still experiencing the same issue.

I can create a new data job, a data source node, and a match codes node, however when I preview the match codes node I can only see the match codes - I can't see any of the original fields. 

This becomes a problem in the practice exercise for 6.3 Clustering Records as it uses the data job created in 6.2, and only the MatchCodes appear in the Available list:

Strangely, when I duplicated the data job, all original fields appear as expected:

Original Job (L06P1_Manufacturers_MatchCodes) – only MatchCode fields appear in Preview

Copied Job (L06P2_Manufacturers_MatchReport) – all fields appear in Preview

And then I'm able to partially complete 6.3, albeit not without errors - initially I received an DQ Plugin error in the Preview tab, then after refreshing the Preview tab populated but only with the new standardized field, not all fields:

Even though I'm following the instructions meticulously, I'm absolutely aware this is most likely user error and I'm happy to be educated/corrected because I have no idea what I'm doing wrong.  I'd greatly appreciate if someone could please help me understand why this is occurring and what I need to do to fix it.

Thanks!

[audrey]

Hi,

So in your MatchCode node, you can go to the "Additional Fields" at the bottom left and there you decide if you want to add some of your input fields because, I think, by default MatchCode node will not pass all the input fields.

I'm puzzled by the duplicating that "fixes" the issue, I don't think I've already seen that. If you'd like to investigate more accurately, maybe open a Tech Support ticket?

Hope this helps,
Audrey