Adding framework components to a solution- automation to add the account number to the combo box

General
, ,
1

I am new toPega.

While doing Pega “Robotics System Architect” course, I am stuck in one of the challenge “Adding framework components to a solution”

I have followed all the steps but still at point # 4- Create an automation to add the account number to the combo box after the interaction starts.

Step 21, after start debugging the application - combo box is not displaying account number 23453.

I want to understand from where it is picking this value and why it is not displaying for me.

Thanks
Shuchi

2

@ShuchiG32 It should be coming from the InteractionStarted event. You might post your solution here and I might be able to offer a suggestion as to what is missing. You would want to zip up your entire solution folder and attach it to your post or a comment if you’d like to share it. I suspect you missed a step earlier in the exercise.

3

@ThomasSasnett thanks for your reply.

The complete folder is around 25 mb so I have shared it in google drive at below location -

Main Solution folder - TrainingCertificationSln.

Also after executing the project, when I click on New Call button in the CRM app it is giving exception - "Error executing link in Automation: CRM_E_CRMChild_Created - From: CRM.CRMlblAcctNum.Properties To: CRM.CRMChild.Properties

The given control and key combination already exists."

When I am closing New Call window, it is giving below exception -
"Error executing link in Automation: CRM_E_CRMChild_Closing - From: CRM.CRMlblAcctNum.Properties To: _GC_CRM.IntMgr.CloseInteraction()

Could not find instance from KeyProvider. KeyName: Key KeyProviderName: IntMgr"

4

@ShuchiG32 You can delete the “bin” and “obj” folders from your solution before zipping and it will be much smaller. Please do that and attach.

5

@ThomasSasnett Thanks, it worked. I had interrogated the wrong item.

6

@ThomasSasnett I believe your issue is that you have interrogated the wrong item for the account numbe; specifically your control CRMlblAcctNum is pointing to the wrong control in the application. You should interrogate the actual account number (which is of a control type label) instead of the label with the text “Account Number”. When you open a new customer window, you would get an exception because you are starting an interaction for a key that already exists since your key is “Account Number” instead of whatever the customer’s account number is. I hope this helps.