No Snapshot records could be found to create your File Commit.

When trying to commit in a user story, you might see the warning below after clicking on the Commit Files button.

User-added image

There are 2 reason why this warning can be displayed even though you know the Git Snapshot record exist.

1. The Git Snapshot Permissions in the Git Snapshot has been set to: "Allow Snapshots Only". This will prevent the Git Snapshot from being used to commit files. Only Full Snapshot are allowed.

User-added image

2. The user trying to commit doesn't have visibility on the Git Snapshot record. Although it's recommended, not every user committing files must have their own Git Snapshot record. They just need to have visibility on the existing Git Snapshot for the Org Credential of the user story.

- Why the user doesn't have visibility on the Git Snapshot?

Like with any other object in Salesforce, if a user doesn't have access to a record, it's like that record doesn't exist for that user. Git Snapshot is a child record of Org Credential object. Any git snapshot is linked to an org credential record. If the user doesn't have access to the org credential record linked in the user story, the user will not have access to the git snapshot linked to that org credential.

- How can you solve or prevent this issue from happening?

1. The user owns an Org Credential record for that environment and also a Git Snapshot linked to his/her own Org Credential record.

2. The Org Credential record used in the User Story is shared with Read/Write permissions with the user that is trying to commit in the user story.


 

How did we do?