Digital-Clay Community Forum

We have an entity table of companies/organizations and a contact table (linked to entity) for the associated contact people.

A particular user X was working on a specific entity. He selected the tab which displays the entity's contacts. When he double clicked on a particular contact, clay closed completely without warning.

So far, this has not happened to X for other entities or contacts.

When another user Y accessed the same problematic contact on Y's computer with Y's username and password, he was able to open the contact normally.

When user Y accessed the same contact on X's computer by signing into clay with Y's username and password, he again was able to open the contact normally.

When user X accessed the same contact on a different computer by signing into clay with X's username and password, the error appeared--as soon as he double clicked on that contact, clay closed completely without warning.

Therefore, it appears to be a user profile problem.

Thoughts? Suggestions? How can we prevent this from happening?

For bugs, always report what version you are on please. I understand you are using an alpha so I suggest you update the version recently (if you haven't already) to see if the problem has been fixed.

Please also let me know what permissions X has/hasn't on the Contact table that Y does/doesn't. I.e. assuming X and Y are using two different roles, compare the permission differences and let me know.

Yesterday we updated to 9.0.0a67.

X is defined as a "User"
Y is defined as an "administrator"
Z, a "User" (who tried on Z's computer) also had the same error.

Looks like permissions problem?

Users are able to read, add, change, merge and set owner for any contact. Administrators seem to be able to do everything.

Got it thanks. It'll be fixed in the next alpha.

When is that? What number?

9.0.0a70 probably middle or end of next week

Another instance of the phenomenon: A different "user" tried to create a contact today and the system closed completely.

Logic suggests that this is connecting to the problem described last week.

Could you let us know when the fix will be ready? Thanks.

The fix is ready.