Integrated BIM tools, including Revit, AutoCAD, and Civil 3D
Professional CAD/CAM tools built on Inventor and AutoCAD
Different code blocks expect different data types attempting to snap the wrong data type to a code block won't work. So having an understanding of the data types helps us become comfortable working with code blocks.
Type:
Tutorial
Length:
5 min.
Transcript
00:03
Different code blocks expect different data types
00:07
attempting to snap the wrong data type to a code block won't work.
00:11
So having an understanding of the data types
00:14
helps us become comfortable working with code blocks.
00:18
Here we have four code blocks relating to a height parameter.
00:22
The parameters values block expects a list
00:26
or collection of data.
00:28
The list can be composed of any of the other data types.
00:32
In
00:32
this example though it includes just two pieces of numeric data
00:38
The next block is a value block and expects a numeric data type.
00:43
Third in the list is a label block which expects a text data type. In
00:48
this case, the word length,
00:51
the last block is a read only block which sets a
00:55
parameter to be editable or not editable in the form.
00:60
This block expects a true false data type.
01:03
Here we modify each block to see how it relates to the form.
01:08
First, adding a new number value of seven to the list
01:12
with a click of the update button. We see our new value.
01:16
Next we change the number for the values block
01:20
just as an example to understand how we set a new value
01:24
onto the label block. We change the text to read, hello world,
01:29
we update the form and see the change.
01:33
We'll quickly change that back to read length
01:36
so that the label makes more sense.
01:39
Lastly,
01:40
we'll change the read only block to be true and see how it impacts the form
01:45
quickly. We'll change that back to false so the user can input values
01:51
next,
01:52
we'll add a new parameter block and see how it handles data type changes.
01:58
First, we'll pull a number block from the math category of code blocks
02:03
and snap it to the parameter value block.
02:06
In addition to accepting a simple number block,
02:09
the value block will also accept mathematical equations.
02:14
We'll move the eight down into the new block and then set it up to subtract one.
02:20
Let's take a look at what happens when we change the block from value
02:24
to the plural values.
02:26
Notice that the block kicked out the equation block since
02:30
values expects a list data type and not a numeric.
02:34
Attempting to snap the numeric equation back to the values block is of no use as
02:40
it is smart enough not to accept a data type that could generate an error.
02:45
Maybe it's the equation.
02:47
Will it take a number?
02:50
Nope, it won't.
02:52
Let's try a string of text.
02:55
We'll pull a basic text block from the text category
02:58
of code blocks and set it to read test.
03:02
Nope,
03:03
the values block does not accept string values, either
03:07
a glance at the example above. And we see that the values block expects a list.
03:14
We'll pull a create list with block from the list category of the code blocks
03:19
and attempt to snap it to the values block.
03:23
Finally,
03:24
we have matched the values block with a block of the data type. It expects to receive
03:31
notice that the list block will accept the different data type blocks.
03:36
What happens if we change the block from a values block to a label block?
03:42
The labels block kicks out the list block.
03:46
Will it take a number?
03:48
Nope,
03:49
maybe a text block then
03:52
indeed,
03:53
the label block wants a text data type to hand to the form label.
03:58
Finally, we'll change the block to a read only block and run it through the same tests
04:05
just so we can understand how the various block types expect different data types.
04:11
This helps us learn to recognize the way that code blocks kick out incompatible data
04:17
and block them from snapping together to prevent data type mismatch errors.
04:23
In summary, different code blocks expect different data types
04:28
attempting to snap an incompatible data type to a code block is prevented.
04:33
The general code block, data type categories are text numeric lists and true false.
Video transcript
00:03
Different code blocks expect different data types
00:07
attempting to snap the wrong data type to a code block won't work.
00:11
So having an understanding of the data types
00:14
helps us become comfortable working with code blocks.
00:18
Here we have four code blocks relating to a height parameter.
00:22
The parameters values block expects a list
00:26
or collection of data.
00:28
The list can be composed of any of the other data types.
00:32
In
00:32
this example though it includes just two pieces of numeric data
00:38
The next block is a value block and expects a numeric data type.
00:43
Third in the list is a label block which expects a text data type. In
00:48
this case, the word length,
00:51
the last block is a read only block which sets a
00:55
parameter to be editable or not editable in the form.
00:60
This block expects a true false data type.
01:03
Here we modify each block to see how it relates to the form.
01:08
First, adding a new number value of seven to the list
01:12
with a click of the update button. We see our new value.
01:16
Next we change the number for the values block
01:20
just as an example to understand how we set a new value
01:24
onto the label block. We change the text to read, hello world,
01:29
we update the form and see the change.
01:33
We'll quickly change that back to read length
01:36
so that the label makes more sense.
01:39
Lastly,
01:40
we'll change the read only block to be true and see how it impacts the form
01:45
quickly. We'll change that back to false so the user can input values
01:51
next,
01:52
we'll add a new parameter block and see how it handles data type changes.
01:58
First, we'll pull a number block from the math category of code blocks
02:03
and snap it to the parameter value block.
02:06
In addition to accepting a simple number block,
02:09
the value block will also accept mathematical equations.
02:14
We'll move the eight down into the new block and then set it up to subtract one.
02:20
Let's take a look at what happens when we change the block from value
02:24
to the plural values.
02:26
Notice that the block kicked out the equation block since
02:30
values expects a list data type and not a numeric.
02:34
Attempting to snap the numeric equation back to the values block is of no use as
02:40
it is smart enough not to accept a data type that could generate an error.
02:45
Maybe it's the equation.
02:47
Will it take a number?
02:50
Nope, it won't.
02:52
Let's try a string of text.
02:55
We'll pull a basic text block from the text category
02:58
of code blocks and set it to read test.
03:02
Nope,
03:03
the values block does not accept string values, either
03:07
a glance at the example above. And we see that the values block expects a list.
03:14
We'll pull a create list with block from the list category of the code blocks
03:19
and attempt to snap it to the values block.
03:23
Finally,
03:24
we have matched the values block with a block of the data type. It expects to receive
03:31
notice that the list block will accept the different data type blocks.
03:36
What happens if we change the block from a values block to a label block?
03:42
The labels block kicks out the list block.
03:46
Will it take a number?
03:48
Nope,
03:49
maybe a text block then
03:52
indeed,
03:53
the label block wants a text data type to hand to the form label.
03:58
Finally, we'll change the block to a read only block and run it through the same tests
04:05
just so we can understand how the various block types expect different data types.
04:11
This helps us learn to recognize the way that code blocks kick out incompatible data
04:17
and block them from snapping together to prevent data type mismatch errors.
04:23
In summary, different code blocks expect different data types
04:28
attempting to snap an incompatible data type to a code block is prevented.
04:33
The general code block, data type categories are text numeric lists and true false.
Here we have four code blocks relating to a height parameter.
The parameters values block expects a list or collection of data.
The list can be composed of any of the other data types.
In this example, though, it includes just two pieces of numeric data, ten and eight.
The next block is a value block and expects a numeric data type.
Third in the list is a label block which expects a text data type. In this case, the word length.
The last block is a read only block, which sets a parameter to be editable or not editable in the form.
This block expects a true false data type.
Here, we modify each block to see how it relates to the form.
First, adding a new number value of seven to the list.
With a click of the update button, we see our new value.
Next, we change the number for the values block, just as an example, to understand how we set a new value.
On to the label block, we change the text to read Hello World.
We update the form and see the change.
We'll quickly change that back to read length so that the label makes more sense.
Lastly, We'll change the read only block to be true and see how it impacts the form.
Quickly, we'll change that back to false. So the user can input values.
Next, we'll add a new parameter block and see how it handles data type changes.
First, we'll pull a number block from the math category of code blocks and snap it to the parameter value block.
In addition to accepting a simple number block, the value block will also accept mathematical equations.
We'll move the eight down into the new block and then set it up to subtract one.
Let's take a look at what happens when we change the block from value to the plural values.
Notice that the block kicked out the equation block. Since values expects a list data type and not a numeric.
Attempting to snap the numeric equation back to the values block is of no use. As it is smart enough not to accept a data type that could generate an error.
Maybe it's the equation. Will it take a number?
Nope. It won't.
Let's try a string of text.
We'll pull a basic text block from the text category of code blocks and set it to read test.
Nope. The values block does not accept string values either.
A glance at the example above and we see that the values block expects a list.
We'll pull a create list with block from the list category of the code blocks and attempt to snap it to the values block.
Finally, we have matched the values block with a block of the data type it expects to receive.
Notice that the list block will accept the different data type blocks.
What happens if we change the block from a values block to a label block.
The labels block kicks out the list block.
Will it take a number?
Nope. Maybe a text block then.
Indeed.
The label block wants a text data type to hand the form label.
Finally, we'll change the block to a read only block and run it through the same tests just so we can understand how the various block types expect different data types.
This helps learn to recognize the way that code blocks kick out incompatible data and block them from snapping together to prevent data type mismatch errors.
In summary, different code blocks expect different data types attempting to snap a incompatible data type to a code block is prevented.
The general code block data type categories are text, numeric, lists, and true false.
How to buy
Privacy | Do not sell or share my personal information | Cookie preferences | Report noncompliance | Terms of use | Legal | © 2025 Autodesk Inc. All rights reserved
Sign in for the best experience
Save your progress
Get access to courses
Receive personalized recommendations
May we collect and use your data?
Learn more about the Third Party Services we use and our Privacy Statement. May we collect and use your data to tailor your experience?
Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.