Date Formatting
In the event that your .CSV import has a different format for the Start Dates and End Dates than yyyy-MM-dd, Hoylu will flag the field for review so you can use this Table of Tokens to help Hoylu recognize the format.
In the case of Figure 4, the date format in the .CSV is Sunday, May 26, 2024, and so it must be modified.
-
Click on the triangular warning sign beside the mapped field
-
Use the Table of Tokens to identify which token(s) you need to use based off the example format (in the case of Figure 2, it is DDDD)
-
Type in the Token in the open field
- Click the Confirm button that now appears since the conflict has been resolved
🚧 Warning: .CSV exports from different software may necessitate other functions like combining tokens or unmerging data from cells, which can grow complex. Please feel free to reach out to Support@Hoylu.com for further assistance.
Table of Tokens
| Standalone Token | Format Token | Description | Example |
|---|---|---|---|
| d | Day of month, no padding | 6 | |
| dd | Day of month, padding to 2 | 06 | |
| c | E | Day of week, as number from 1-7 (Monday is 1, Sunday is 7) | 3 |
| ccc | EEE | Day of the week, as an abbreviated localized string | Wed |
| cccc | EEEE | Day of the week, as an unabbreviated localized string | Wednesday |
| ccccc | EEEEE | Day of the week, as a single localized letter | W |
| L | M | Month as an unpadded number | 8 |
| LL | MM | Month as a padded number | 08 |
| LLL | MMM | Month as an abbreviated localized string | Aug |
| LLLL | MMMM | Month as an unabbreviated localized string | August |
| LLLLL | MMMMM | Month as a single localized letter | A |
| y | Year, unpadded | 2022 | |
| yy | Two-digit year | 22 | |
| yyyy | Four- to six-digit year, pads to 4 | 2022 | |
| kk | ISO week year, unpadded | 22 | |
| kkkk | ISO week year, padded | 2022 | |
| W | ISO week number, unpadded | 32 | |
| WW | ISO week number, padded to 2 | 32 | |
| D | Localized numeric date | 9/6/2022 | |
| DD | Localized date with abbreviated month | Sept 6, 2022 | |
| DDD | Localized date with full month | September 6, 2022 | |
| DDDD | Localized date with full month and weekday | Wednesday, September 6, 2022 | |
| f | Short localized date and time | 9/6/2022, 1:09 PM | |
| ff | Less short localized date and time | Sep 6, 2022, 1:09 PM | |
| fff | Verbose localized date and time | September 6, 2022, 1:09 PM | |
| ffff | Extra verbose localized date and time | Tuesday, September 6, 2022, 1:09 PM |
You can find additional tokens here.
Upstream or Downstream Connection Formatting
If your Predecessors and Successors are not importing properly or the fields are highlighting in red, you may need to adjust the expression of the connections via the RegEx format.
-
Click on the triangular warning sign beside the mapped field
- Edit the Regular Expression so the resulting Task ID format matches the Task ID format in your .CSV file
In Figure 3, the Regular Expression removes the Connection Information FS-10days so only the valid Task ID "1" remains.
WARNING
Scenario 1:
Depending on the formatting of your Activity ID, you may run into other errors including Hoylu not recognizing a dependency configuration within the Activity ID.
In most cases the easiest way to fix this it to type in:
.*in the Regular Expression ID field in order for Hoylu to understand that is the entire Activity ID string, not a dependency configuration.
Scenario 2:
If you have an Activity ID that has spaces between the ID number, the connection type, and the lag/lead, you will also receive warnings because Hoylu will not recognize spaces in the ID string, so you will need to remove them within the CSV file.
You may run into various scenarios similar to this, so please do not hesitate to reach out to your Customer Success Manager or Support@Hoylu.com for assistance.
Comments
0 comments
Please sign in to leave a comment.