microsoft / microsoft/Dynamics-365-FastTrack-Implementation-Assets

Failure try to create _viewreplacement

Open
#204 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jupyter Notebook
Stars
494
Forks
296
Avg merge
1d 10h
Merged PRs (30d)
5

Description

Hello,
I get the following error code on the activity "CreateMetadataView":
{
"errorCode": "2011",
"message": "File '/ReplaceViewSyntax.json' cannot be opened because it does not exist or it is used by another process.",
"failureType": "UserError",
"target": "CreateMetadataView",
"details": []
}
I don't understand where this file "ReplaceViewSyntax.json" should be created but I found the step in the activity where this file is needed.
It relates to the creation of the _viewreplacement meta data view. First there is a creation with plain dummy values and in the next step there is a try to alter the view based on the data out of the missing "ReplaceViewSyntax.json" file on the lake.
I don't understand why this crashes because the whole statement to alter the view is included in a try block.

My hotfix was to delete the whole try block to alter the _viewreplacement meta data view and everything worked fines as before.

I get this error in different customer environments all using the newest version of cdmutil. So it would be nice if anyone can fix this error with cdmutil.

Kind regards
Tobias

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the CreateMetadataView activity and trace how it references /ReplaceViewSyntax.json while creating the _viewreplacement metadata view. Check the cdmutil workflow and the surrounding try block to determine why the missing file still produces a failure. Done means the activity handles the missing file correctly and the metadata view is created or altered successfully.

Written by the indexing model from the issue text.

Assessment

Domain
data
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.