Import lineups

Built lineups in another tool? Import the CSV and DFS Hero turns it into a build tab. The new build works like a build you ran here: simulate it, rank it, pin and trash lineups, swap, fill your entries, and export.

Before you start

• Open the slate the lineups are for. The import matches each player to this slate's players.
• The file is a CSV with a header row. The header names the roster slots in roster order, for example QB, RB, RB, WR, WR, WR, TE, FLEX, DST on DraftKings NFL Classic.
• These files work:
  • A lineup file from another tool, in the format the site's bulk upload reads.
  • A file that DFS Hero exported.
  • A DraftKings or FanDuel entries file with lineups filled in. The import takes the lineups and ignores the entry and contest columns.
• Each lineup cell needs the site's player ID. The import reads a bare ID, Name (ID) (DraftKings), and ID:Name (FanDuel). A cell with a name and no ID does not import.
• On a Showdown slate, the first lineup column is the Captain or MVP.
• A second header row in the file, from two exports pasted together, is passed over.
• A build holds up to your plan's lineup limit: 500 on Essential, 10,000 on Power.

Import a file

1. Open the import. Use one of these:

   • Click + next to the build tabs, then Import lineups.
   • Drop the CSV anywhere on the workspace. A file with the roster's columns and no Entry ID column opens the import. An entries file uploads as entries, as before.
   • On a tab with no lineups, click Import lineups in the Lineups panel.
   • On a phone, you can also open Tools, then Import Lineups.

2. Drop the CSV on the dialog, or choose a file. Before you pick, the dialog shows the slate, the columns the file needs in order, and a link to this page.

3. Read the report. Its first line counts each lineup in the file one time: how many will import, how many are duplicates, the lineups whose players are not on this slate, how many have a file error (an empty cell, a cell with no player ID, or a player ID this slate does not hold), and how many the site would refuse (a player in a slot he cannot play, a player twice, salary over the cap, or a site rule). Once DFS Hero looks those players up, that part splits into lineups "from another slate" and lineups "not on any slate". Below it:

   • The first two lineups that will import, seat by seat, with each lineup's salary and projection. Each one reads like "#1 · line 2": its number in the new build, the same number the Lineups panel shows, and its line in the file.
   • Will not import: first the lineups from another slate. The report names the slate that holds their players, with its site and how many lineups it holds, for example "4 lineups are from DraftKings NBA Main". Open DraftKings NBA Main opens that slate with the same file in Import lineups, read against that slate's players, so one more click imports it there. Then each lineup that does not import, with its line number in the file and the reason. The list scrolls; a shadow at its edge shows that more rows sit past it.
   • Rows of an entries file with no lineup yet are not counted as lineups.

   Enlarge

4. Change the build name if you want. It starts as the file name, selected, so you can type a new name or press Enter.

5. Click Import N lineups. A build tab opens with the lineups. On a computer, the Lineups panel opens beside it. When you start from a tab that was never built and that you did not change, the import fills that tab. A tab that holds a build, or your own changes to it (players, settings, lineup count, Selection, name, note, or Contest Setup), stays as it is, and the import opens a new tab beside it. A tab you made with + counts as unchanged when it copied no player edits from your build; settings it copied are no change. Player edits it copied (locks, exposures, projections, excludes) count as changes, so the import keeps that tab. An edit you undid, such as a lock you turned off again, is no change.

The projections come from this slate's player pool, the same numbers the grid shows. Projection or ownership columns in your file are ignored. The new build starts with blank Build Settings: no stacks, exposure caps, locks, or excludes.

Skipped lineups

The import skips a lineup it cannot use, and says why. A file error is the file's own fault:

• A slot is empty, or a cell has no player ID.
• A player ID is not on this slate.

The site would refuse the other skipped lineups:

• A player cannot play the slot of his column.
• A player is in the lineup twice.
• The lineup is over the salary cap.
• The lineup breaks a site rule, such as too many players from one team.

Click Download these rows to get a CSV of every lineup that did not import, with a Reason column. Fix the rows in your tool and import them as a second build. To join two builds, use Combined builds.

Duplicates

The same players count as one lineup, whatever slots they sit in. The import keeps the first copy and lists each later copy with the line it repeats. On a showdown slate, the same players with a different Captain or MVP are two lineups.

Tips

• Import every file for a slate as its own build, then combine the builds.
• Simulate the imported build to rank its lineups against the slate's contests. See Run your first simulation.
• Fill and export work as on any build. See Contest setup and fill.

Troubleshooting

"We could not find the lineup columns." : the file has no header row with the roster's slots in order. Add one, or export the file from your tool in the site's upload format.

"This file holds Showdown lineups. This slate is Classic." : open a slate of the file's type and import the file there.

"This file has no filled lineup rows." : the file has a header and no lineups, or it is an entries file with every entry still empty. Fill the lineup columns and import it again.

"N lineups would import. Your plan allows M per build." : split the file into parts of M lineups or fewer, and import each part as its own build. On the Essential plan, the dialog also links to the plans page: the Power plan allows more lineups per build.

"This file is not a CSV." : save the file as CSV (comma delimited) in your spreadsheet app, then import it again.

Every lineup is "from another slate" : the file is for a different slate. Before the report finds the slate, each of these rows reads "No player in this lineup is on this slate." Use the Open button in the report: it opens that slate with the same file ready to import. Or find the slate in the Day View. A lineup that is "not found on any slate" has player IDs that no slate holds; check the IDs in your tool.