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
- All Categories
- 1.2K Product Ideas
- 1.2K Ideas Exchange
- 1.4K Connect
- 1.1K Connectors
- 273 Workbench
- 2 Cloud Amplifier
- 3 Federated
- 2.7K Transform
- 78 SQL DataFlows
- 525 Datasets
- 2.1K Magic ETL
- 2.9K Visualize
- 2.2K Charting
- 437 Beast Mode
- 23 Variables
- 513 Automate
- 115 Apps
- 390 APIs & Domo Developer
- 8 Workflows
- 26 Predict
- 10 Jupyter Workspaces
- 16 R & Python Tiles
- 332 Distribute
- 77 Domo Everywhere
- 255 Scheduled Reports
- 66 Manage
- 66 Governance & Security
- 1 Product Release Questions
- Community Forums
- 40 Getting Started
- 26 Community Member Introductions
- 68 Community Announcements
- 4.8K Archive