# Sample project on Flex repeater

**URL:** <https://forum.inductiveautomation.com/t/sample-project-on-flex-repeater/21989>\
**Category:** Ignition Early Access\
**Created:** [January 18, 2019, 10:18pm UTC](https://forum.inductiveautomation.com/t/sample-project-on-flex-repeater/21989 "2019-01-18T22:18:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sudipta.tripathy](https://avatars.discourse-cdn.com/v4/letter/s/c57346/32.png) [@sudipta.tripathy](https://forum.inductiveautomation.com/u/sudipta.tripathy)\
**Post date:** [January 18, 2019, 10:18pm UTC](https://forum.inductiveautomation.com/t/sample-project-on-flex-repeater/21989/1 "2019-01-18T22:18:28Z")

</div>

I was wondering if you have a sample project on Flex Repeater. I have a need to render a list of machines on with query tags (Output, yield, machine states …) on a perspective view.

---

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [February 7, 2019, 11:57pm UTC](https://forum.inductiveautomation.com/t/sample-project-on-flex-repeater/21989/2 "2019-02-07T23:57:52Z")

</div>

This depends on a myriad of variables, but first let me get some clarification…

Do you have one query tag which houses all of your needed information? Or do you have multiple tags which each have information about one machine? I have to be honest - I’m not sure how to go about this if you have multiple tags which house all of the needed information… If you do have just one tag, this is very easy and I can create a couple of Views to show you how it’s done.

To use a Flex Repeater, you just need to specify a path to a View and supply an array of instances to repeat.

The path to the View is straight-forward enough - just create a “template” View which displays the information you want and set PARAM properties for each value you want represented. Then, place some sort of display component in the View for each of those PARAM properties and bind the value of the component to the PARAM property it will represent (the components will be blank unless you provide a default/fallback value for each PARAM property).

The FlexRepeater.props.instances array of objects is the tricky part, but basically you want to make a new instance for each of your “machines”, and each machine should be made up of key:value pairs where the key is a case-sensitive match for one of the PARAM properties in the “template” View.

---

<div class="post-metadata">

**Author:** ![joe.friedrich](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/joe.friedrich/32/7505_2.png) [@joe.friedrich](https://forum.inductiveautomation.com/u/joe.friedrich)\
**Post date:** [February 8, 2019, 12:16pm UTC](https://forum.inductiveautomation.com/t/sample-project-on-flex-repeater/21989/3 "2019-02-08T12:16:34Z")

</div>

Paul's sample project might help:

> [@Swiping Cards in Perspective](http://forum.inductiveautomation.com/t/swiping-cards-in-perspective/21402/2):
>
> The important part (at least, re: swiping) is actually a carousel. I’ve attached an extremely basic example with two different pages in a carousel - each is actually the same view, but with a different number of ‘cards’ visible. The ‘Card’ view is just a coordinate container; then the ‘Page’ is a flex container with a flex repeater within it. On the ‘Landing’ view, the carousel is set to ignore the default view height and width, then then also set to take the entire space available in its contai…