Upload Recommendations

Use this page to upload recommendation records in bulk, review uploaded file history, and manage upload rules for recommendation data.

Asset mapping in Recommendation

The application automatically links Cloud Recommendations to the appropriate Asset (Application, Service, or Product) during the upload process.

Recommendations are matched using Resource ID as the primary identifier.
Asset association is determined using a priority order of Application Tag, Service Tag, and Product Tag.
The association process runs automatically for both manual file uploads and Advanced integrations.
Existing manual associations are preserved and take precedence over automatic associations.

For more information, refer Automatic asset association for Recommendation.

Overview

Use bulk upload when recommendation records already exist outside Yarken or when a team needs to load many recommendations at once.

Uploaded recommendations appear in the Recommendations workspace and can be reviewed, filtered, edited, dismissed, actioned, and included in savings reporting.

The upload workflow supports recommendation files in .xlsx and .csv formats.

Before you begin

Before uploading recommendation data, confirm that:

The recommendation file is available in .xlsx or .csv format.
Required fields such as Recommendation ID, Source, Category, Details, Status, Complexity, and Value are available or can be mapped.
Resource ID (Recommended for manual file upload): Ensure your file includes the unique Cloud Resource ID (e.g., AWS ARN or Azure Resource ID). This enables the system to automatically associate the recommendation with the correct Asset.
For automatic asset association, confirm that:
- The recommendation file contains the cloud Resource ID.
- Cloud Consumption data has already been loaded for the affected resources.
- Application, Service, or Product tags are populated in the Cloud Consumption records.
- Tag values match existing asset names in Yarken.
The recommendation can still be imported when these conditions are not met, but it will not be automatically associated with an asset.
Asset type, asset code, cloud account, and cloud resource values match the way your organization records those values in Yarken.
Potential and realized savings values are numeric where provided.
Recommendation dates use a consistent date format.
Any repeat transformation requirements are handled by upload rules where appropriate.

If the recommendations come from a cloud provider integration, configure the connection and pipeline instead of manually uploading provider exports unless your process requires a one-time manual load.

Upload a recommendation file

To upload recommendations:

Go to Admin > Recommendations.
Select the Details tab.
Select Upload.
Drag and drop the file into the upload window, or select Browse.
Select the file you want to upload.
Complete any mapping or validation steps shown during upload.
Finish the upload.
Open the Uploaded Files tab to confirm the file status.

After the upload is complete, successfully loaded recommendations are available on the Details tab.

Review uploaded files

The Uploaded Files tab shows recommendation upload history.

Use this tab to confirm whether a file loaded successfully, review record counts, and identify files that need correction.

Common columns include:

Column	What it shows
Year	Year associated with the uploaded file, where available.
Month	Month associated with the uploaded file, where available.
File Name	Name of the uploaded file.
Destination	Destination table or area, such as Recommendation.
File Type	Type of uploaded file.
File Status	Current processing status, such as Loaded or Error.
Loaded Records	Number of records successfully loaded.
Total Records	Total number of records found in the file.
Error	Error information where the file did not fully load.

Use Add Filter to narrow uploaded files by destination, period, status, or other available fields.

Uploaded file actions

Uploaded file actions help administrators review, correct, and reload recommendation data.

Action	Use it to
Download	Download the uploaded source file for audit, review, or correction.
Reload	Process the file again using the current mapping.
Remap and Reload	Update the mapping and reload the file when fields were mapped incorrectly.
Delete	Remove an uploaded file record where permitted.

Use Remap and Reload when the uploaded file has the right data but the column mapping needs correction.

Upload Rules tab

The Upload Rules tab is used to maintain rules that transform, validate, or enrich recommendation data during upload.

The application uses default upload rules for the application, product, and services tag extraction

The system's built-in Automated Asset Association executes post-ingestion and complements your custom upload rules. It uses the Resource ID to resolve assets based on a priority hierarchy: Application Tag > Service Tag > Product Tag.

Upload rules are useful when repeat files need consistent changes before records are loaded into the Recommendations workspace.

Use upload rules to:

Set default values for missing fields.
Standardize field values across uploads.
Update a field during upload.
Apply repeat transformation logic.
Reduce manual cleanup after upload.

The Upload Rules table may include fields such as source table, field to update, rule type, rule, comment, updated date, and updated by.

Create an upload rule

To create an upload rule:

Go to Admin > Recommendations.
Select the Upload Rules tab.
Select Add New.
Select the Source Table.
Select the Field to Update.
Choose the Rule Type.
Define the rule.
Add a comment where it helps other administrators understand the rule.
Select Save.

Test upload rules with a controlled file before relying on them for recurring recommendation loads.

Validate an upload

After uploading a file, validate the result before using the data in reports.

Open Uploaded Files.
Confirm the File Status is Loaded.
Compare Loaded Records with Total Records.
Review any error count or error message.
Open the Details tab.
Search for a sample of uploaded recommendation IDs.
Confirm the expected source, category, status, savings, asset, and cloud resource values.
Run Cube Refresh from the bottom of the Admin menu after a successful upload, reload, remap and reload, or upload rule change.
Open the relevant dashboard, report, or Analytics view to confirm reporting reflects the uploaded data.
Correct and reload the file if required.

If a file shows Error or loaded record counts are lower than expected, correct the source file or mapping and upload again.

Validate automatic asset associations

After the recommendation import completes:

Open Admin > Recommendations.
Select the Details tab.
Find a sample of the imported recommendations.
Confirm that Cloud Resource ID contains the expected resource.
Review Asset Type and Asset Code.
Confirm that the recommendation is associated with the expected Application, Service, or Product.
Open the relevant asset or Application Portfolio view and verify that the recommendation appears.

When the asset fields are blank, compare the recommendation Resource ID with Cloud Consumption data. Then verify that the selected Application, Service, or Product tag exactly matches an existing asset name.

Refresh after uploads or rule changes

Run Cube Refresh from the bottom of the Admin menu after recommendation data has been uploaded, reloaded, remapped and reloaded, or changed through upload rules.

Cube Refresh helps refresh internal data so uploaded recommendation values are reflected more quickly in the Recommendations workspace, Home dashboard savings cards, Recommendations Overview, and Recommendations Data.

Troubleshooting uploads

If uploaded recommendations do not appear as expected, check:

The file is in a supported format.
Required columns are present or mapped.
Recommendation IDs are populated and unique.
Source, status, complexity, value, and category values use accepted values.
Potential saving and realized saving values are numeric.
Date values use the expected format.
Upload rules did not overwrite fields unexpectedly.
The file status and record counts on Uploaded Files match expectations.
Cube Refresh was run after the upload, reload, remap and reload, or upload rule change.

Use Remap and Reload when field mapping is the issue. Use a corrected file upload when the source data itself is incomplete or invalid.

Recommended practices

Keep upload templates consistent across teams.
Use stable recommendation IDs so repeat uploads do not create confusion.
Review file status after each upload.
Run Cube Refresh after upload, reload, remap and reload, or upload rule changes.
Check record counts before relying on dashboards or Analytics outputs.
Use upload rules for recurring cleanup, not one-off exceptions.
Keep comments on upload rules clear enough for another administrator to understand.
Retain downloaded copies when needed for audit or reconciliation.

Next step

Set up Recommendation Integrations

Related content

Recommendations

Manage Recommendations

Set up Recommendation Integrations

Recommendations Data