Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×
The Claris Museum: The Vault of FileMaker Antiquities at Claris Engage 2025! ×

This topic is 7255 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

I'm sure I'm making this harder than it needs to be...

I have three files: Clients.fp5 (one record per customer), Invoices.fp5 (multiple records per customer) and Statements.fp5 (one record per customer). Each customer has a unique ClientCode.

I would like to open a portal in Statements.fp5 to show ONLY the customer's unpaid invoices from the Invoices.fp5 file.

The relationships I was hoping to use to accomplish this didn't work because the fields couldn't be indexed. It works if I base the relationship on a manually entered invoice open/closed status, but who wants to do that?

Any thoughts on how best to tackle this problem would be appreciated.

Posted

I'm sure I'm making this harder than it needs to be...

I have three files: Clients.fp5 (one record per customer), Invoices.fp5 (multiple records per customer) and Statements.fp5 (one record per customer). Each customer has a unique ClientCode.

I would like to open a portal in Statements.fp5 to show ONLY the customer's unpaid invoices from the Invoices.fp5 file.

The relationships I was hoping to use to accomplish this didn't work because the fields couldn't be indexed. It works if I base the relationship on a manually entered invoice open/closed status, but who wants to do that?

Any thoughts on how best to tackle this problem would be appreciated.

Posted

I'm sure I'm making this harder than it needs to be...

I have three files: Clients.fp5 (one record per customer), Invoices.fp5 (multiple records per customer) and Statements.fp5 (one record per customer). Each customer has a unique ClientCode.

I would like to open a portal in Statements.fp5 to show ONLY the customer's unpaid invoices from the Invoices.fp5 file.

The relationships I was hoping to use to accomplish this didn't work because the fields couldn't be indexed. It works if I base the relationship on a manually entered invoice open/closed status, but who wants to do that?

Any thoughts on how best to tackle this problem would be appreciated.

Posted

I have a calculation field called InvoiceStatus which just looks at the invoice balance. If there's a zero balance, the result is "Closed" otherwise it defaults to "Open."

Posted

I have a calculation field called InvoiceStatus which just looks at the invoice balance. If there's a zero balance, the result is "Closed" otherwise it defaults to "Open."

Posted

I have a calculation field called InvoiceStatus which just looks at the invoice balance. If there's a zero balance, the result is "Closed" otherwise it defaults to "Open."

Posted

Creat relation to all Invoices.Then by script try to set option in related records which makes this record not visible in portal if this Invoice is Closed. I tried it at last time.

Posted

Creat relation to all Invoices.Then by script try to set option in related records which makes this record not visible in portal if this Invoice is Closed. I tried it at last time.

Posted

Creat relation to all Invoices.Then by script try to set option in related records which makes this record not visible in portal if this Invoice is Closed. I tried it at last time.

This topic is 7255 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.