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 8283 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

If you do not have a copy of the cdml reference db you should get it from fm's website. Using it can broaden your understanding.

This example is from "Current Token"

[FMP-If: CurrentToken:5.eq.{CurrentToken:6}]

Adapt it to meet your needs.

Posted

I'm not knocking the advice you gave -- everyone should have (and learn to use) the CDML Tool. It's the best help we've got. But your example reminds me that I think I'm seeing a certain number of errors in it.

For example, I just successfully used this:

[fmp-if: currentFoundCount .lt. {currentRecordCount}]

But if you go over the description of [fmp-if] in CDML Reference.fp5, the allowable expressions in the third parameter are quite limited compared to the first parameter, and replacement expressions like {currentRecordCount} or {CurrentToken:6} are not among them.

It keeps insisting on "literal values" -- but isn't that an error? Or am I reading it wrong?

Posted

The code you originally presented: [FMP-IF: TicketN.eq.[FMP-CurrentToken]]

The code example I responded with: [FMP-If: CurrentToken:5.eq.{CurrentToken:6}]

The code which you "just successfully used": [fmp-if: currentFoundCount .lt. {currentRecordCount}]

The example I presented used curly brackets. The code you originally presented used square brackets. The code which was successful for you uses curly brackets.

The brackets were the point. I'm glad you got it.

This topic is 8283 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.