We use 3000 as the year for "forever" it shows in data preview but not in the final dataset
Our employee team assignments are dated with a start and end date. If it is their current assignement, the date is 1/1/3000. I discovered that when I bring the data in through workbench with a select *, it recognizes it as a date column and displays 01-01-3000 in hte data preview but when the dataset is created, it is null.
I tried an if statement using the year function and returning 2099-1-1. This worked but now I have an extra column. Is there a way to edit the validation rules?
Comments
-
What version of Workbench are you using? I'm running some tests on this, but if I knew the version it would help with the testing. Thank you in advance!
1 -
Workbench 4
I ended up doing a replace in a transform to replace the year with something in hte future that still looks like a year to Domo - 2099. It would be nice if the definitions of what Workbench considers an error were listsed somewhere. or even better were configurable... Sorry for the delayed response.
0
Categories
- 10.8K All Categories
- 3 Private Company Board
- 1 APAC User Group
- 12 Welcome
- 38 Domo News
- 9.7K Using Domo
- 1.9K Dataflows
- 2.5K Card Building
- 2.2K Ideas Exchange
- 1.2K Connectors
- 343 Workbench
- 258 Domo Best Practices
- 11 Domo Certification
- 464 Domo Developer
- 50 Domo Everywhere
- 105 Apps
- 714 New to Domo
- 85 Dojo
- Domopalooza
- 1.1K 日本支部
- 4 道場-日本支部へようこそ
- 26 お知らせ
- 64 Kowaza
- 299 仲間に相談
- 653 ひらめき共有