Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Nested InlineActions

Featured Replies

I have an [FMP-InlineAction] tag on a web page, and I use the [FMP-Record] tag to loop through the found set. Within the loop, I have a [FMP-CurrentRecordNumber] tag. It returns the correct value on the website itself, but it doesn't evaluate when I put the intratag form as a token in a nested [FMP-InlineAction] as follows:

[FMP-InlineAction: -db="firstdatabase.fp5", -lay="Layout #1", Field="find_value", -Find]

[FMP-Record]

[FMP-CurrentRecordNumber] <---This evaluates correctly

[FMP-InlineAction: -db="seconddatabase.fp5", -lay="Layout #1", Field="find_value", -token="first_token", -token.1={FMP-CurrentRecordNumber}, -Find]

[FMP-CurrentToken: 1] <---This doesn't evaluate

[/FMP-InlineAction]

[/FMP-Record]

[/FMP-InlineAction]

Am I doing something wrong?

I would try it in series.

  • Author

I would, but the page I'm making has a nested format and needs to retain the [FMP-CurrentRecordNumber] order.

Ok. Then if I am reading your code correctly:

[FMP-InlineAction: -db="seconddatabase.fp5", -lay="Layout #1", Field="find_value", -token="first_token", -token.1={FMP-CurrentRecordNumber}, -Find]

you are trying to pass two tokens and performing a -find in seconddatabase.fp5 using the value "find_value" in the field Field.

Is the find being successful?

I'm not sure on how important it is to define the first token as -token.0="first_token" instead of as -token="first_token", even though -token used by itself supposedly defaults to -token.0

If [FMP-CurrentToken: 1] is not being evaluated/displayed, it may not have been captured, and therefore not passed.

Finally, it may be that what you are attempting is not possible, in part or in its entirety. Perhaps others will offer more help.

  • Author

The find is successful. I tested it out using just one token (i.e. -token={FMP-CurrentRecordNumber}), and it still doesn't pass the value.

I believe that the Token will hold the value assigned from the calling page; not from the InlinAction. I could be wrong here however, that is what I have experienced so far.

Good Luck.

Garry

Off the top of my head, would it help if you put [FMP-Record]...[/FMP-Record] tags within your innermost InlineAction?

  • 4 weeks later...

IMHO it wouldn't work.

Inline is complete and separate process. You create something (result) you can display and reuse within the same Inline. Then it is forgotten 100%.

You can store result in token and use it on next page.

It is down to design. I will call your way cheap and FM doesn't buy this.

Why don't you use portal for such thing? You don't have to do the second search.

RE: Inline is complete and separate process. You create something (result) you can display and reuse within the same Inline. Then it is forgotten 100%.

any values derived from the first inline should be available in the opening Inline tag of the nested inline ...... tokens from one, in Lasso anyway, are not available in the other. Think of them as format files within format files when trying to pass values from one to the other .... this is why Lasso have introduced the named inline then the values can be called by the inline name.

If used properly with other features like portals they can be very powerful

cool.gifsmile.gif

Create an account or sign in to comment

Important Information

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

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.