New range of wireframe components live in wireframe library 🚀

I agree with other comments here that this feature is effectively unusable in the current state. While wireframes don’t need to convey visual styles they need to convey the functional elements that will appear on the page, and this includes the column names for a table. I’ve tried the table component but this does not have a similar look and feel to the other wireframe components so requires a lot of fiddling to get working. For me this has meant that I will not be using Miro Wireframes and will use another tool for wireframing as it isn’t yet fit for purpose.

The usability issue arises from the fact that it deviates from the principles of the Miro Wireframe library.
While elements like buttons and tabs in the library can be customized in terms of solidity, style, and functionality (e.g., solid/line/text/enabled/disabled for buttons and normal/selected/disabled for tabs), the Data Table does not seem to align with this flexibility.
It appears less usable to me, although it may suit some users, particularly those with specific requirements like having precisely three columns and an icon in the header

I did a workaround by duplicating the datatable element but would love to see it as a feature. +1

+1 for adding and removing columns. It is significantly more difficult to get the point across to stakeholders if you constantly need to explain all their requested columns will be present in the final feature. 

Adding request for adding columns to data table

I’d like to revive this thread. 

My use case is designing a relational database. Each table in this relational database needs to show column names (fields), and a few example rows. 

The “Table” component is not a replacement for the wireframe “data table” because I cannot easily draw arrows showing the relationships between fields of different tables. (If there is, let me know please) 

Meanwhile, the “wireframe data table” has this capability. Unfortunately it does not allow me to add columns (fields) easily, which is extremely important for my use case. 

Adding request for adding columns to data table

Another request to add column, unusable in current form

If the regular table is enough to build a prototype / wireframe, any reason why Miro creates a redundant component “data table” in the wireframe session?

@Henrik Ståhl I think it’s comments like yours above that cause stakeholders to acquire a distaste for lean agile.

Irrespective of your personal views on wireframing (and for what it’s worth, I agree), it’s for users to decide how they view / wish to use different system components. Ever seen that video of the QA sticking all the different shapes in the same shaped hole?

A is table bi dimensional, x and y. Having an option to add row and not columns is a bit odd to me.

@janet smith I still don't understand why it would be “useless”, that's a very harsh statement. Personally, I'd say it's highly ineffective to replace proper communication between people with detailed wireframes/mockups, but let's just agree to disagree! It's always interesting to discuss these things though.

Totally agreed with @John Knowles . It’s pretty useless.

I don’t use Data Table just for visual presentation. I need to label the columns. 
Same things goes to “text input” and “button”, they are meant for mocking visually, but without able to label them, it is useless.

Haha, you're right. I agree to disagree!

It is an option, but that data table component is not designed for wireframes.  Whereas the wireframe components are easier to work with, require less manipulation. 

Lets just agree to disagree 

It’s not a data table component though. It’s a data table wireframe component. I still don’t quite understand why using the regular table — which is an actual data table component, not a wireframe component — isn’t an option here?

It seems one persons nice to have is another persons should have in this case.

Suppose it depends on your design system, processes etc. Our wireframes need to contain all the functional parts of the feature/page/screen.

This data table component could save a good amount of time, if columns could be added to it, rows can be added after all.

If you applied the “no columns on tables” mentality to all the UI elements in MIRO it wouldn’t be as great as it is!

Hopefully MIRO will take this data table  MVP and make an MLP ;-)

I wouldn’t say it’s “useless” since it’s still just a simple visualization that should come with additional information. It’s a wireframe, not a blueprint. But I understand that it’s a nice-to-have.

Ok, so its not useless if your interface has a functional need for a 3 column table.

@John Knowles Yeah, but again – it’s for wireframing. Wireframing is just a way to display the functional elements of an interface. I can see that being able to add columns is a nice-to-have, but I don’t quite understand why the lack thereof would render the entire wireframe component useless? 

Tables often have more than 3 columns, a regular table doesn’t have the pre-formatting that this feature provides.

Just curious, why is the feature “not usable” without the ability to add and delete columns? I mean, it is for wireframing, after all. If it’s so important to have the exact amount of columns and rows in a simple wireframe, why not use the regular table? 

+1 for adding columns, this feature is not usable without it.

AND don’t forget to include deleting columns!

+1 Adding column to wireframe data table.  Feature not usable in current state.

Adding columns in the wireframe data table would be a great feature and will save a lot of time on prototyping!