I am building an Event Log. The Setup:

Client Table: Client Id, Event Level 1, Event Level 2, Event Level 3

Event Log Table: (Same fields).

The Tables are tied, based on the Client Id. All good & simple.

I have a portal for the Event Log. Originally, I created the Event Level Fields, in the Client Table, as simple Numbers.

I filtered the Portal, based on the Event Level Selections. Originally, it shows all Events. If you select Level 1, it shows only Level 1 Events that you select. Same for the other two Levels.

All well & good. However, this means that all users are seen the same view of the Portal. Not a good way to go.

I converted the Event Level Fieids in the Client Table to Global Numbers. In Relationships, this works just fine. However, the Portal Filter just completely breaks down. I can't get the Filtering to do anything with the Global Numbers.

This just seems odd & wrong. Anybody have any experience with this?

Can you explain the Event Level 1, Event Level 2, Event Level 3 business? What does it mean, and why does it require three fields?

Well, Level 1 would be things like (Collections, Accounting, Correspondence, ...).

Level 2 breaks down each of these. For Collections it could be Last Call Made, Skip Trace, Public Records Search, ...)

Level 3 breaks ever further. For Skip Trace, it would be something like Initiated, Found New Address, Located, Closed.

We can add further Levels, if required. Three should due though, at least for a few years.

Just an organized way to break down events/notes. The Portal is supposed to make it clean & easy to filter out the information you need. Not a new idea. Works great for viewing large amounts of information & tracking your workflow.

Much easier for the user than doing Finds/Searches.

Works great, as long at the Level Ids are not Globals.

Why don't you post a file - preferably a simple one - showing the problem?

I apologize for not getting back. I've been overloaded, with a lot of new work.

I added another level to my Events this weekend, adding EventCorrespondence Tracking, building on the Event Table. I had some problems getting it to work.

In the end, I had to use the Event Table for a portal, even though I was working with the EventCorrespondence Table. I better understand how FileMaker ties its Relationships together. It is similar to a traditional SQL Database but differs some when we go to implement it in the GUI.

This problem probably has to do with how I setup the Portal. If I get a chance to get back to it later, I'll post a follow up.

Thank you for trying to help.