​@Shana 
 

When you're importing lag durations in AdaptiveWork, here's how to make sure they’re set correctly depending on whether you want to count workdays or calendar days:

To control how the lag is calculated, include the Duration Type in your import file:

• Choose "Default" if the lag should count only working days (skipping weekends and holidays)

• Choose "Consecutive" if the lag should count all calendar days (including weekends and holidays)

For example:

• If you want 5 workdays of lag: Lag = "5d", Duration Type = "Default"

• If you want 5 calendar days of lag: Lag = "5d", Duration Type = "Consecutive"

Just make sure both the Lag and Duration Type fields are included in your file so the system can apply it correctly.

The Entity DependencyLink does not include a field called “Duration Type” (Metadata Explorer), and when I upload a file, I get this error on that column: 

Field 'Duration Type' not found in the entity 'DependencyLink', the entire column will be ignored

Where do I import the ‘Duration Type’ information?

Also, when I import Lag in the form of, say, ‘120ed’, the Data Loader reads that as ‘120 Days OverrideEnd’. What is that about?

Thanks for your response. 

You're correct that the lag type is specified directly in the duration format since there's no separate "Duration Type" field in the DependencyLink entity:

Standard Format:

• 5d = 5 working days (business days only)
• 5ed = 5 elapsed days (calendar days including weekends/holidays)

The error 120 Days OverrideEnd suggests the Data Loader may not be properly interpreting the 120ed format, which could be due to several factors:

Quick Test: Before diving deeper, try importing a single dependency with a smaller elapsed day value like 5ed to confirm whether this is a format issue or something specific to the larger 120-day duration.

If the test fails: This appears to be a system-specific Data Loader issue that would benefit from direct review. I'd recommend opening a support ticket with:

• Your import file sample
• The exact error message
• Your current field mappings

The support team can examine your specific environment and file structure to identify whether this is a format limitation, validation rule, or configuration issue.

If the smaller test works: There may be validation limits on lag duration values that need to be addressed through your system settings.

Thank you for following up. I have been meaning to post my successful results. Turns out, ‘ed’ is not how you do it. Its ‘cd’. Here is an example of a dependencylink data load sheet that worked for me. Make sure you verify which is the ‘WorkItem’ and which is the ‘DependsOn’, because I originally had it switched around. 

Thank you for sharing your solution and the helpful tip on verifying the ‘WorkItem’ and ‘DependsOn’ fields.