Formatting excel data types for family parameters

Revit
1

Hi - I’m trying to format some excel data for input into family type parameters (that are shared), and keep getting “The parameter’s storage type is not a number”. In the screenshot, I have compared the object.type for both my excel data and the parameter storage types - they appear to match, other than the python node outputting System.* types instead of native Revit integers, doubles, etc. Is that what is causing the issue? You can ignore IN[0] in the python, it’s not doing anything yet.

# Load the Python Standard and DesignScript Libraries
import sys
import clr
clr.AddReference('ProtoGeometry')
from Autodesk.DesignScript.Geometry import *

# The inputs to this node will be stored as a list in the IN variables.
famtypes = IN[0]
params = IN[1]

# Format parameters
for param in params:
	# ID
	param[0] = str(param[0])
	# Name
	param[1] = str(param[1])
	# Depth
	param[2] = float(param[2]/12)
	#Height
	param[3] = float(param[3]/12)
	# Width
	param[4] = float(param[4]/12)
	# Weight
	if param[5] == None:
		param[5] = 0
	else:
		param[5] = int(param[5])
	# Counter or Floor
	if param[6] == None:
		param[6] = ''
	else:
		param[6] = str(param[6])
	# Relocated?
	if param[7] == None:
		param[7] = 0
	elif param[7].lower() == "y":
		param[7] = 1
	else:
		param[7] = 0
		
	# Location
	if param[8] == None:
		param[8] = ''
	else:
		param[8] = str(param[8])
	# Power
	if param[9] == None:
		param[9] = 0
	elif param[9].lower() == "y":
		param[9] = 1
	else:
		param[9] = 0
	# Dedicated Circuit
	if param[10] == None:
		param[10] = 0
	elif param[10].lower() == "y":
		param[10] = 1
	else:
		param[10] = 0
	# BTU
	if param[11] == None:
		param[11] = 0.0
	elif param[11].lower() == "y":
		param[11] = 1.0
	else:
		param[11] = 0.0
	# Water
	if param[12] == None:
		param[12] = 0
	elif param[12].lower() == "y":
		param[12] = 1
	else:
		param[12] = 0
	# Drain
	if param[13] == None:
		param[13] = 0
	elif param[13].lower() == "y":
		param[13] = 1
	else:
		param[13] = 0
	# Computer
	if param[14] == None:
		param[14] = 0
	elif param[14].lower() == "y":
		param[14] = 1
	else:
		param[14] = 0
	# UPS
	if param[15] == None:
		param[15] = 0
	elif param[15].lower() == "y":
		param[15] = 1
	else:
		param[15] = 0
	# Printer
	if param[16] == None:
		param[16] = 0
	elif param[16].lower() == "y":
		param[16] = 1
	else:
		param[16] = 0
	# Notes
	if param[17] == None:
		param[17] = ''
	else:
		param[17] = str(param[17])
	

# Assign your output to the OUT variable.
OUT = params

Equipment Creator_2022-02-28_09-28-52
Equipment Creator_2022-02-28_09-28-522423×1910 299 KB

2

Should these just be 1 & 0 like the rest without the .0?

1 Like
3

Duh…yep. Overzealous copy and pasting on my part!

1 Like
4

Actually, I’m still running in to the same error with that bit fixed. Indices 2, 3, and 4 are decimal inches/12 in the Python script, but they are for 3 length parameters in the family type. Do I need to do any conversion to get usable project units from those? I’m thinking that’s the issue.

5

Can you share an image with the error and results visible? Everything looks good from what I can see this far, unless one of your IF statements is throwing a null somewhere.

6

Yep, here you go. The setparameter node is giving nulls for the length parameters and all of the yes/no’s.

Equip Creator
Equip Creator5296×2022 549 KB

7

I would go through and try to set each one individually. I would also try to remove the float() and divide by 12.0 to force the double. I now see False and True, did you change from 1 and 0 for the Yes/No parameters?

8

Yeah, I think that’s what I’ll have to do. I did switch the yes/no to boolean outputs to see if that worked w/ the parameters, but both True/False and 1/0 give me a null in the setparameter node. In the past I haven’t run in to this issue when formatting excel data for parameters, but it sure is giving me trouble on this - probably one value that is messing it up.

1 Like
9

@SeanP so I’ve gone through and tested each parameter one by one, and they all work just fine - but when I run them all at once, the error comes up. Any idea of whats going on to cause that? Lacing/list structure?

1 Like
10

It may be a string to number conversion issue steming from excel maybe? I’ve seen that time to time.

1 Like
11

That should cause one of the parameters pop up as an error when executed individually though, right? None of them did.

1 Like
12

Is there any chance you could share a sample mode, family(s),and data set?

1 Like
13

I actually gave up on the setparameter node and handled all the parameter setting/update in the Python node. Works perfectly now :slight_smile: Thanks for helping!

1 Like
14

I thought about suggesting that, but wanted to try and answer the question asked, but good choice!

1 Like