# Block inputs and outputs **URL:** \ **Category:** Ideas & Features\ **Tags:** blocks\ **Created:** [October 24, 2021, 10:33pm UTC](https://community.fibery.io/t/block-inputs-and-outputs/2140 "2021-10-24T22:33:41Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [October 24, 2021, 11:08pm UTC](https://community.fibery.io/t/block-inputs-and-outputs/2140/2 "2021-10-24T23:08:55Z")
Interesting idea! I know that Michael said [doing in-line calculations/variables should not be too hard](https://community.fibery.io/t/in-dev-migrate-entity-view-to-blocks/2005/13), and they would consider it. I am curious if you can provide a more typical-Fibery example use case for the functionality you’re describing. What came first to my mind, though it may not be an example of what you had in mind (and may not be that useful, or the best way to handle it), is a “CSV Import” _block_, which basically shows a spreadsheet-like view of a specified CSV in-line on the page, and then allows you to directly reference those values elsewhere. This is advantageous over the much heavier current approach of importing CSV data into some Type (or creating a Type for it), and could help address some of the various requests around here for more ad-hoc data handling. It’s a half-formed idea, but I’m curious if this maps at all to what you were contemplating. And certainly I’m interested in other examples if you have any. --- _[View the full topic](https://community.fibery.io/t/block-inputs-and-outputs/2140)._