Hi Aaron,

You could have a look at the MultiType Datatype. It will allow you to create multiple rows or simple data and looks nice and simple for the client.

Or if you already use uComponents you could upgrade to the latest version and there is a datatype called DataType Grid. I haven't used it but I think its very similar to MultiType.

Ben

Thanks very much. I have installed and set up the MultiType datatype, but when I browse to the content tree I get an asp error:

Multiple controls with the same ID 'mySpecs' were found. FindControl requires that controls have unique IDs.

I've tried renaming the data type field but the error comes back with the new name replacing 'mySpecs'.

Any suggestions or tips would be awesome, this seems like it's just what I need if I can get it working.

Hey,

If you can't get MultiType working I can 2nd the recommendation the uComponents DataType Grid, I use it alot.

Rich

Did you get the 1.1.1 version? I thought I had fixed this problem.

Thanks
Ben

The only way I can reproduce this error is if I add two properties to a document type and both have the same alias. If this is the case then change the alias of one of the properties as you should have unique alias' on your document types.

Ben

yep, I just double checked the packages screen and it reports 1.1.1

I tried adding it to another site on another server but got the same thing.

Edit: there is definitely not another property with the same alias on the document type (or even on any other document type).

unrelated question - when you've added multiple entries, is it possible to re-sort them in the content pane or would that need to be done via a sort field and xslt?

I tried ucomponents but it's killed the whole site. (not a problem it was a clean install)

thanks again for the help

Very strange, could you describe what you did after installing the package? If I can reproduce the error then I will have a better idea about how to fix it for you.

As for sorting, once you've added multiple items then the content editor can move them about so they are in a different order and they must press save to save them in that order. Then you must craete an xslt which contains something like this:

<xsl:for-each select="$currentPage/labelsAndValues/Items/Item">
    <xsl:sort select="./@sortId"/>
</xsl:if>

This makes use of the sort order that gets saved with each item.

Thanks
Ben

Sure, I'll go through all the steps I took because I'm not a programmer.

- downloaded the zip for 1.1.1 and installed local package. Confirmed all messages (binary files etc.), successfully installed.

- went to the data types section, and created a new data type called myDataType. left the limit field alone (on zero) and added a couple of properties, both text fields with different names and aliases.

- went to the document types, and added a 'myDataType' control to the textpage document type. Gave it a unique name and alias. Saved the document type.

- browsed to the content tree, and selected a text page. That's where I see the error in the right-hand side content pane. If I remove the control from the document type and go back to the content tree, it all shows up normally again.

This is running on an older version (4.6 I believe), so if you'd prefer I can try reinstalling it with 4.7 and trying the above again.

Hmm that could be the problem, I've built everything against umbraco 4.7.

When I created the package it would only let me say it was compatable with 4.5+ but now I see it can be 4.7 I will change it when I release my updated code. Hopefully this weeked :S

You could try umbraco 4.7 I fairly confident it will work because it does for me.

Thanks
Ben

I'll replace my install with 4.7 over the weekend and let you know how it went. Thanks a ton for looking into this.

I've installed this on a 4.7 and no issues this time around.

Sorry - edited my question because I found the answers I was looking for in the package details. This is working great, thank you.

Hey,

I will eventually get round to making some proper documentation for this package. 

Have fun with it. Any problems let me know.

Thanks
Ben 

is working on a reply...