first, this is probably one of the best "I've got a problem" post on this forum - ever ;)

I just mimiced a setup using the info in your screen shots (which are all correct, btw) and I can get .pyFirstName to behave.

Try this: delete that text input, then save the EmployeeInformation record. Close it. Then reopen it and try to add the text input again.

eddie

Haha thanks.  Gotta help you help me =]

Anyways, I had no luck with that approach.  However, for some reason it's accepting .pyLastName now, but still not .pyFirstName.  Also when I try to configure the repeating grid for the section "Dependents Information", it still won't accept either .pyFirstName or .pyLastName.  

Both data classes are definitely referencing Data-Party as their directed parent.  

I was stuck at the same point, and in the same way, so I added a DataParty page to Pages & Classes, with Class of DataParty. I was a kludge, but it provided access to .pyFirstName and .pyLastName.

Since seeing this forum topic, I deleted those fields and the Page from the section, closed and reopened the section, and now the .pyFirstName and .pyLastName work.

Is this behavior common in the PVS or this release?

Thanks for the suggestion Tom.  Unfortunately this did not work for me.  

Jason,

I would not be opposed to a WebEx or Lync meeting. What you and Tom are experiencing is perplexing - let's chat ;)

Private message me to exchange email addresses.

eddie

Minnie,

if I understand this correctly, you are working on the EmployeeInformation section in SAE-HRServices-Data-Employee. And, you are adding a repeating grid for the Dependents information, but cannot access the Relationship and DOB properties.

Confirm the following:

- you have a Dependent data class with the context of SAE-HRServices-Data-Dependent. At least the Relationship and DateOfBirth properties are defined in this class.

- you have a Dependent page list property defined in SAE-HRServices-Data-Employee; along with the other employee-related properties.

eddie

The source of the repeating grid is Dependents, so when I try to set a property,

shouldn't the drop down show the Dependent properties instead of Employee ?

My question is should I be setting the properrty value to .Relationship (since the source of the grid is Dependents) or .Employee.Dependents.Relationship?

Dropdown doesn't have .Relationship, it only shows .Employee.Dependents.Relationship.

ah - this makes it a whole lot easier ;)

that dropdown is not lying to you.

an .Employee has at a .Dependent of a certain .Relationship

You have to maintain the context of the relationship of the dependent to the employee

eddie

When  I try  to set the value to .Dependents.Relationship, I get the follwoing error :

But, shouldn't it be .Employee.Dependent.Relationship ?

.Dependents.Relationship is predicated upon .Employee; at least it should be.

Minnie,

Feel free to email me directly at [email protected]

It might prove faster than this forum. We can always post back here our resolution

eddie

Hi Eddie,

I was able to resolve it. It looks like I was adding the control to the top row (label) insteas of the bottom row :)

Thanks!

awesome.

I am making a note to myself to make that the third of the first three things I check for ;)

eddie