Calculated Field - User Defined Table Module [Lead: Sebastian Leupold]

Forum DotNetNuke® Pro... User Defined Ta... Calculated Field

8/13/2006 2:38 PM

	Stefan Cullmann
1431 posts

Re: Calculated Field

Robert,

first study the generated XML, this will help you writing your stylesheet:
http://dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/56/threadid/57044/scope/posts/Default.aspx

You will discover that

the column names gets xml encoded -> [Transaction Type] will be <Transaction_x0020_Type>
you will find an addional element <Date_UDT_Value> which contains the formated date for your [Date] column respecting the current localization

Stefan Cullmann - stefan.cullmann [at] dotnetnuke.com

forms & Lists (UDT5.0) will be the next major release of the User Defined Table project.
A first Preview is available, though it requires DotnetNuke 5 (Beta 5).

8/16/2006 4:38 AM

	Robert Belknap
66 posts
www.belknap.us

Re: Calculated Field

Thanks for the rapid response.

I was a little slow at understanding the <Date_UDT_Value> tip, but finally got it. I was looking for a method to define the [date] as a date and was not seeing that that function was already done for me in the <Date_UDT_Value>. Even though you told me...

I am curious as to why there is a difference in the time offsets highlighted below. I would have expected the offset to be the same.

   <Data>
      <UserDefinedRowId>15</UserDefinedRowId>
      <CreatedBy>host</CreatedBy>
      <CreatedAt>2006-08-01T08:05:57-07:00</CreatedAt>
      <ChangedBy>host</ChangedBy>
      <ChangedAt>2006-08-01T08:05:57-07:00</ChangedAt>
      <Date>2004-12-31T00:00:00-08:00</Date>
  ...

8/16/2006 9:20 AM

	Stefan Cullmann
1431 posts

Re: Calculated Field

rbelknap wrote

Thanks for the rapid response.

I was a little slow at understanding the tip, but finally got it. I was looking for a method to define the [date] as a date and was not seeing that that function was already done for me in the . Even though you told me...

Localization of the date is rendered to the XML content because of missing date function in the .NET XSLT implementation.
Otherwise you would need to parse the date as string - which is ugly and don't support localization.

rbelknap wrote

I am curious as to why there is a difference in the time offsets highlighted below. I would have expected the offset to be the same.


      15
      host
      2006-08-01T08:05:57-07:00
      host
      2006-08-01T08:05:57-07:00
      2004-12-31T00:00:00-08:00
  ...

Me too - very strange. I will think about.

12/9/2006 4:54 AM

	Tikkune
198 posts

Re: Calculated Field

Modified By Tikkune on 12/9/2006 9:14:37 AM)

Stefan Cullmann wrote
you will find an addional element <Date_UDT_Value> which contains the formated date for your [Date] column respecting the current localization

Brand new to XML/XSL, I don't understand how to code the date element above. Would someone please show it used in a snippet of .xsl? Thank you.

"If a problem can be solved, there's no use worrying about it. If it can't be solved, worrying will do no good."

12/9/2006 5:55 AM

	Stefan Cullmann
1431 posts

Re: Calculated Field

XSL (without an EXSLT library) doesn't provide any date related functions, they are treated as strings.
The data inside UDT is loaded into a dataset containing multiple tables. The main data is inside the table "data". UDT provides its own datatypes that provide some more features, they are not mapped build in into .Net. We help ourself adding some invisible columns, it depends on the current udt type.
The date data type adds an invisible column containing the localized date as string. This helps you presenting a nice date using xml.
These invisble colums are described in the documentation for UDT3.3.7. (unpublished),
and here http://www.dotnetnuke.com/tabid/795/forumid/56/threadid/69772/scope/posts/Default.aspx

Page 3 of 4

Forum

DotNetNuke® Pro...

User Defined Ta...

Calculated Field