Creating a Mockup is required for any Custom Work Request. The more complete and accurate your Mockup is, the smoother the Custom Work Request will go. Any time the R365 Professional Services Team puts into cleaning up or adjusting the Mockup will be included in billed time. 


Mockup Requirements

The submitted Mockup must include all of the requested columns, calculations, and references to current Radar data. 


Data that is not currently found in Radar cannot be included in Custom Work.


The Mockup consists of two parts submitted together as a single file; a 'Sample File' demonstrating the expected output file and a 'Specifications List'. 


Sample File


The Sample File is a representation of the desired output file. This sample is used to determine if the output file matches the submitted Custom Work Request.

The Sample File is also used for data verification and must contain current Radar data that accurately shows how this data would appear in the Custom Work.


If a Report is requested, any requested formatting must be represented on the Sample File. 

  • Note: Exports do not support color or font formatting. 


For both Reports and Exports, the Sample File should be in .csv or .xlsx file format.


Example Sample File




Specifications List


The Specifications List must contain the following information and match the Sample File:


  • File Name - Name of the file displayed in Radar and the file name when downloaded

  • Mockup Data - The data used to populate the Mockup
    • Database Information
    • Location(s) 
    • Date of Business or Date Range
      • Note: The Mockup should include data as it would appear when the Report or Export is run. If the Report or Export would typically be run for more than a single day, data for the most common date range should be included. 
    • Source within Radar where the data was found

  • File Summary - Information about the file in general, including:
    • Header Row Information
    • File Output Format
    • Conditional Details
    • Step 1 Options - (Location Selection)
    • Step 2 Options - (Date Selection)
    • Step 3 Options - (Data Filter Selection)
      • Important Note: Each Step 3 Option requires additional Development Work, and will increase the cost of the Custom Work.

  • Column Summary - Information about each column in the Sample File, including:
    • What is populated in that column
    • Formatting
    • Calculations

  • Additional Notes - Any additional information that helps explain the Custom Work Request.


Example Specifications List


Sample GL Sales Export

****************

Mockup Data

DB #1765 - Ctuit Radar Training

Location #1 - Sonoma

DOB - 7/25/2021

Source: General Ledger Report

*****************

Include Header Row

Output as CSV Format

Break out GL Posting Activity by GL Sales Rule Name if present for Non-Cash Tenders

Step 1 - Location & Location Group

Step 2 - Open Date Range

Step 3 - N/A


Summary:

Column A - Populate Location Export ID and date formatted as [Location.ExportID][MMDDYYYY] 

Column B - Always populate 'Standard'

Column C - Populate DOB

Column D - Leave Blank

Column E - Always populate 'GL Sales Export'

Column F - Populate Location Export ID

Column G - Populate GL Code Number if GL does not have a value in Force Extension.  If Force Extension has a value, populate that as GL Code. **NOTE** If Multiple GL Codes have same Force Extension Value, Output will provide   Aggregate Total of Debit or Credit.

Column H - Populate total Debit Amount for GL Code in Column G; Leave Blank if Total is Credit

Column I - Populate Total Credit Amount for GL Code in Column G; Leave Blank if Total is Debit

Column J - Populate Location Export ID

Column K - Populate GL Code Name OR GL Sales Rule Name if breakout details present; if GL Code in Column G is Force Extension GL, Populate GL Name associated with that GL Code Number.


ADDITIONAL NOTES:

GL Posting Activity is summarized by GL Code