Audit Trail/Log of changes per user

  • 86Views
  • Last Post 13 April 2021
0
votes
Mickael Dominguez posted this 08 April 2021

Wondering if there is a way to see which user made a change?

We have multiple user on our SkyVia account and about 2 weeks ago one of the users broke one of our packages.
I have been directed by my CEO to find out which user it was that broke the package.
I can see in the Log on the package the day and time it stopped working - but unsure how to tell who ade the changed that resulted in this breakage

Any help would be greatly appreciated

Attached Files

Order By: Standard | Newest | Votes
0
votes
Olena Romanchuk posted this 13 April 2021

Hello Mickael,
We have checked your package again, and we can confirm that the package itself was last modified more than a year ago.
You can check the modification date in your Workspace on the Packages list page.    



 

It looks like the column ActivityId which is mapped in the package was absent or renamed for some time in the SQL Server table dbo.SFDCJobActivities.
Could you please check if there were any changes with the objects on the SQL Server side?

0
votes
Mickael Dominguez posted this 11 April 2021

Hi,
This information seems incorrect. It is my understanding that the package was edited in March
Also, as you can see from the attched screenshot, the Package was working untill March 24th

Can you not see on the back end of your software which of our two users made the change?

0
votes
Olena Romanchuk posted this 08 April 2021

Hello Mickael,

Unfortunately there is no opportunity to monitor who performed changes in the packages for now,
but it is in our roadmap. 

  However we checked your account on our side.
If we have identified the account correctly by your e-mail, we see that there are two users in the account who are able to modify anything.

  We also see that the failing package https://app.skyvia.com/#/45794/packages/77423/debug
was last modified 12/06/2019. And the error says that the column "ActivityId" is not found. Thus please check your source database, maybe there was a field which is not in the database anymore.

Should you have any question do not hesitate to contact us back.

Close