Announcement

Collapse
No announcement yet.

[FEATURE REQUEST] Better support for arrays in CSV DataTables

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • replied
    Originally posted by DamirH View Post
    Finding out how stuff is formated is trivial. Create a data table that has the type you need, enter something then export the table as csv. Look at the resulting .csv file and voila, you now know how to format it.
    Actually I just tried that. It failed. But that's still not documentation of a feature but a hack to figure out that feature. That's why the developer just pointed out that 4.16 contains a fix to that problem. But he's not on the documentation team who are right now asking for input on how to fix things like that. As fast as the engine is expanding they can be a bit overwhelmed. And that's a bad thing as the code team also needs to check documentation to see where things are currently at.

    Leave a comment:


  • replied
    Originally posted by Avelworldcreator View Post
    While that is useful information the short answer so far is "no". You just described acceptable input but not how that input is formatted. This is information that should be under Learn > Documentation. No worries. I know just how much a pain it can be to fully document what you've coded.
    Finding out how stuff is formated is trivial. Create a data table that has the type you need, enter something then export the table as csv. Look at the resulting .csv file and voila, you now know how to format it.

    Leave a comment:


  • replied
    Originally posted by Jamie Dale View Post
    DataTableUtils::IsSupportedTableProperty lists the property types that are supported by Data Tables in general. If a property is in that list then it (and any derived property types) should support import/export.

    As of 4.16 the list is: UIntProperty, UNumericProperty, UDoubleProperty, UFloatProperty, UNameProperty, UStrProperty, UBoolProperty, UObjectPropertyBase, UStructProperty, UByteProperty, UTextProperty, UArrayProperty, USetProperty, UMapProperty, UEnumProperty.
    While that is useful information the short answer so far is "no". You just described acceptable input but not how that input is formatted. This is information that should be under Learn > Documentation. No worries. I know just how much a pain it can be to fully document what you've coded.

    Leave a comment:


  • replied
    DataTableUtils::IsSupportedTableProperty lists the property types that are supported by Data Tables in general. If a property is in that list then it (and any derived property types) should support import/export.

    As of 4.16 the list is: UIntProperty, UNumericProperty, UDoubleProperty, UFloatProperty, UNameProperty, UStrProperty, UBoolProperty, UObjectPropertyBase, UStructProperty, UByteProperty, UTextProperty, UArrayProperty, USetProperty, UMapProperty, UEnumProperty.

    Leave a comment:


  • replied
    Is there any place these import/export formats are fully documented with what types are supported? And I mean individually and not the generic reply "any of class X". I'm going to hazard a guess that the import/export of sets and maps are going to be similar to arrays?

    Leave a comment:


  • replied
    Originally posted by Jamie Dale View Post
    I added map and set support to the Data Table import/export for 4.16.
    Thank you! 4.16 keeps getting better. Just wish it was stable enough for production.

    Leave a comment:


  • replied
    I added map and set support to the Data Table import/export for 4.16.

    Leave a comment:


  • replied
    Apparently the export feature does not work for field with the "Set" attribute. How are those supposed to be formatted in CSV or JSON? How about for fields done as maps?

    Leave a comment:


  • replied
    That's a pretty bad workflow just to re-order some rows

    I'll look into adding that to the editor while I'm working on the other UI improvements.

    Leave a comment:


  • replied
    Well, shut my mouth.

    Exceptional. That will enable me to export my current array-filled data table back to CSV whenever I want to do things like reorganize rows (which I very frequently want to do, and which the current uasset editor doesn't allow).

    Leave a comment:


  • replied
    What format is your data table? If it's a .uasset, I've also added the ability to export those to CSV in the above change

    Click image for larger version

Name:	UE4_ExportAsCSV.png
Views:	1
Size:	102.7 KB
ID:	1071380
    Last edited by Jamie Dale; 03-27-2015, 06:44 PM.

    Leave a comment:


  • replied
    You are truly my hero.

    Now if only there was an easy way to EXPORT my current data table back to CSV, so I didn't have to retype changes by hand...

    ah well! Thank you guys!

    Leave a comment:


  • replied
    This has been done as part of 6af0f20199e5f59d6658d30e00a30900a5463206 (which relies on f715c7fbfac75868e5b744c4b77c1cc022710a6b).

    You can now export, import, and view arrays in both the CSV and JSON DataTable formats.

    For CSV they use our standard property export array format, eg)
    Code:
    "(10,20)"
    "(""String1"",""String2"")"
    For JSON they use a standard JSON array.
    Last edited by Jamie Dale; 03-27-2015, 02:49 PM.

    Leave a comment:


  • replied
    Hi RhythmScript,

    A feature request for this has been added for the engineers to take a look at for future consideration. For your reference the ticket is UE-8294.

    Leave a comment:


  • replied
    Hi RhythmScript,

    Thank you for your request, we will take this into consideration.

    Leave a comment:

Working...
X