Another portal filtering question

[ddreese]

To simplify this, I'm going to say there are two DB files: Significant Other, and CY48.

The CY48 file generates a report to be sent to the state. Part of the report pulls information from the client's "significant others" (i.e. mother, father, siblings, caretaker, etc.).

I need to have a portal showing all the household members, which I just now realized would probably be best to denote with a specific field (Yes/No, checkbox, something).

The portal sits on a CY48 layout (obviously), I just need it to filter and show only the sig others that have the household member field flagged.

I read something about this in a previous thread about creating a global field and creating a relationship with the field that i want to filter. Would the global field be in the same file, or a different file? I'm still very shaky on understanding global fields, how they works, and when to use them. Thanks!

[danjacoby]

You have two files. CY48 is apparently where the report is generated, so that's where the "line items" exist that can be seen in a portal in SignificantOther. So far, so good. Now, assuming that this is as simple as you seem to be saying:

Create a field that you can check if the person in the portal is to be included in the report.

Now, create a calc field in CY48 that returns whatever it is you want to show in the report if the checkfield is checked, and nothing if it isn't.

Of course, if it ain't that simple, you'll need to explain just what it is you want included in the report.

[ddreese]

I think you might have it backwards (I apologize if I'm wrong). The significant other file holds all the significant others for each particular case. I need this data summarized and viewable from my CY48 file.

The portal will sit on the CY48 layout, and show records from the significant other file. The records will show in the portal only if the field 'household member' is 'yes'.

So from your post above:

"Create a field that you can check if the person in the portal is to be included in the report."

- I believe I did that, with the 'household member' field

"Now, create a calc field in CY48 that returns whatever it is you want to show in the report if the checkfield is checked, and nothing if it isn't."

- I don't think I know what you meant by this. Create a field in my CY48 file to summarize the data that is flagged in the significant other file? I don't think that's what I'm looking for.

[ddreese]

Well, I came up with a solution. It works, hopefully it's not terribly inefficient or anything

I created a household member calc field in each file. In Sig other, it takes the Case_ID field (used to identify which case it belongs to) and attaches the value of the household member field (either a yes or no).

Then in my CY48 file, I created a similar field with Case_ID and attaches "Yes", and then built the relationship to the significant other file that way. The portal uses that relationship, and boom. All is well.