After You Transition

• Dates may need to be formatted or adjusted. Look under Spreadsheets below for additional details.

• Paragraph spacing  before and after may need to be reviewed or adjusted. To check for this, run a PDF comparison between your classic and next gen files. If you see persistent spacing issues, especially near tables, at the beginning or end of a section, or next to multi-column layouts, contact your CSM or Support for assistance.

• Headers and footers may display differently in next gen compared to classic in some circumstances. You may need to adjust odd/even options or margins to ensure spacing and that everything appears as you'd expect.

• Document names may need to be updated since the next gen Document is new, it will not have a “(1)” at the end of the name like the Classic Documents when it's copied.

• Section names have 100 character limit and the section name may be truncated during transition.

• Shared data validation lists become regular lists and may need to be recreated.

• Table titles are removed as next gen documents do not support table titles, but do support table header rows. The text in classic table titles is kept during transition and placed above the table in the document.

  If you have a secondary table title, you can use the Title Suffix in table properties to enter text, such as "Continued". To learn more, see Set Table Properties.

• Table of contents need to be reviewed to ensure hyperlinking is applied correctly.

• Extra or blank pages may occur due to a mismatch in section margins. Check the margins on adjacent sections and adjust margins on one section to match other page margins. After this, the blank page should go away.

• Symbol alignment, such as an extra space before the percent sign, may appear differently in some cases in next gen Documents. This generally happens when Symbol Align is set to Right and Use parentheses for negatives are both checked under Formats. To resolve this, update Symbol Align to achieve the desired outcome.

• Formulas should be reviewed after transition to make sure they are correct. You can use Document Health as well as looking for #VALUE for any formula issues.

• Dates may need to be reformatted as dates are treated differently in Spreadsheets. In Spreadsheets, dates are treated as a serial date value, which allows you to do more math on dates in Spreadsheets.

  Most dates should transition correctly, but it is best practice to review dates after transition to ensure they are formatted correctly and any calculations using them are still correct.

• Spreadsheet names may need to be updated since the next gen Spreadsheet is new, it will not have a “(1)” at the end of the name like the Classic Workbook when it's copied.

• Sheet names have 100 character limit and the section name may be truncated during transition.

• Shared data validation lists become regular lists and may need to be recreated.

After you transition, you may encounter a few scenarios where links are broken. Review the scenarios below for steps to follow when you encounter broken links.

• Existing broken links: At times, when you transition a classic file, there may already be broken links. You'll typically see transition report code 326. In this scenario, double check your classic files for broken links. Fix your links in your classic files and then re-run your transition.

• Source file not transitioned: If a source file isn't included in the transition, it could break links in desination files. You'll typically see transition report code 300. As a best practice, start your transition from the Linked Files Report to ensure all linked files are included in the transition.

• Waterfall charts now store the total columns as a separate series and corresponding row in the chart table. If this 2nd series is turned into a waterfall the chart will position the columns on either side of the tick marks because it is expecting to have 2 sets of waterfall data now. To fix this, select the last column and change it back to a column series.

• Total labels in classic were a sum of the as-displayed values that represented each data point. In next gen, due to rounding, there may be times when adding up the display value of each data point won’t add up perfectly to the total label. If you’d like your data labels to visually foot to your total labels, we recommend using adjustment columns.

• Review and update your XBRL profile, including the taxonomy, calendar, and company information. Be sure to update your fiscal calendar to reflect your new reporting dates. After you set up the fiscal calendar, select it in the XBRL profile for your document.

• Set default units and accuracies of your document. Each tagged number in a document requires a unit of measure. Using default units and accuracies, you can set units and accuracies that facts will use by default for an XBRL profile.

• Check your document outline. Disable XBRL from sections other than your financial statements and notes. You can disable XBRL at the section level to exclude it from XBRL generation and validation for the document.

• Go through your DEI section ensuring that all your dates are presented as 'Period' value format. All DEI date value Source links should also be formatted as Period. This sometimes requires the use of the =TEXT formula.

• Generate XBRL and clear all validation errors and warnings.