Datacard refuses to allow other datacards on same row

[Peakoverload]

I'm a total newbie to PowerApps, until 3 days ago I'd never even heard of them but I've now stumbled into creating one and hit a snag. Apologies if I'm not using the right terminology here, still trying to find my feet, but I've got an app for a custom form I've created. One of the fields in the form is Due Date.

My powerapp is laid out in 3 columns and I have snap to columns enabled (I've tried disabling this but it makes no difference)

If I add the datacard for this field to my app I can place it next to an existing datacard in the same row. However lets say I then add it to a new row. When I do this, I can't add any other datacards to that row, everything has to be on a new row below or above. If I drag any other field I get the crossed red circle symbol. I can't see anything different in the properties of this datacard to any other so can't work out what I'm doing wrong. As I say I've tried turning snap off but that makes no difference.

In a similar vein can you also do any of the following because I can't find a way of doing it?

1. Leave one column empty in a row. So lets say you have 6 fields in a 3 column layout. Row 1 you want datacards 1-3 but on Row 2 you want datacards 4,5 but you want to leave the middle position empty. Row 3 you want datacards 6,7 but you want the first position to be empty. I've kinda created this effect by simply making the datacard width so wide that it prevents another one being added to the row but it looks and feels 'clunky'.

2. Add different backgrounds behind certain datacards. I have a series of fields that are date related. I'd like to display them together with a different background to other fields. I know you can add a background to the form screen but that's the entire screen. I just didn't think you could add other non form elements within the form area.

3. Position forms wherever you want. For example have 4 fields on one row, one on another, 2 on another etc etc

[LooseChippings]

Hi @Peakoverload 

You can do all the above once you understand data card positioning.  Data cards have an X and Y property.  If you create an app with Snap to columns = 3, The first card is X=0, Y=0; the next card is X=1, Y=0.  So the X,Y positions would be:

0,0	1,0	2,0
0,1	1,1	2,1
0,2	1,2	2,2

However, you cannot create a blank space just by increasing the X number.  If you want an empty space, create a blank Custom Card and move it to the place you want the space.

As you have discovered, if you increase the width of a card beyond the grid size, it will push the following cards to the next row.  Card are always in grid (think of Excel rows and and columns).  If you increase the width of column or height of a row, it affects the all the other cards.  If Snap to columns is turned on, increasing the width of one card will have the same effect as merging two cells in Excel. 

If you turn off Snap to columns off, you can create virtually any layout you wish.  Cards will still be in a grid, but you can move the DataCardKey and DataCardValue fields within the Card to create the layout you need.

Cards have a Fill property, so if you want to group your Date fields together and give them a different coloured background, just change the Fill property on the Date cards.

You can also move the position of Cards by dragging them in the Edit Fields property of the form:

[Peakoverload]

Ahh, I was thinking the x,y coordinates were screen positions i.e. pixel position relative to top left of the window 🤔 Oops. Well that certainly explains a few other things as well. That's a great help, thank you so much.

[LooseChippings]

Yes, it is only with Data Cards where the X,Y sets the relative position.  With everything else, it is the pixel position. 

[Drrickryp]

Hi @Peakoverload 

If you get too frustrated with the OOB form experience, check out @Meneghino 's blog post https://baizini-it.com/blog/index.php/2017/09/28/powerapps-101-create-your-own-forms/ .  You will learn alot about how PowerApps works by going through the exercise of creating a custom built form.  IMHO, it should be required reading for anyone getting serious about designing PowerApps.