capeterson / grey-tab Goto Github PK

Grey tab currently uses a background page to cache organization metadata and internal log messages. There's an alternative, event pages (and the alarms API to replace our use of setInterval()) which only live as long as they need to and don't trigger this warning.

It's a fair bit of code to update, and we'd have to cache in localStorage or the like, but it should lower memory use and fix the scary message about running when chrome is fixed that shows up on windows.

Could not load extension from 'C:\Users...\Sites\Grey-Tab'. Could not load icon 'icon.png' for browser action.

If a user has access to a lot of fields, the query for the record's data can come back with the exception "QUERY_TOO_COMPLICATED: Query is either selecting too many fields or the filter conditions are too complicated.". The popup in the extension says "undefined" but that is the error behind the scenes. Could you do multiple requests for the field data, limiting each query to the max number of fields allowed per query, then combine all of the data in the end? It's frustrating when users can use this great extension feature on certain objects but then can't on others.

As a user i'm too lazy and dumb to use deductive reasoning. Do it for me :)

This was temporarily removed due to it showing improper results in some cases. This will be readded along with more UserInfo details in the future.

If your session to an organization expires and a new session is issued for the same user/org combination the old sessionId will be used, which causes an exception due to the invalid session.

Restarting chrome or disabling and re-enabling the extension is a workaround but quite ugly.

It's annoying and clutters your javascript console. Should fix that.

Hello ,

The Grey tab is not working with sandboxes recently.

When we open the tab is shows ads below.
Org Id: undefined
Host: hostname
SessionId:

On record detail page it shows
An error occured trying to load record details: undefined

Hi,

I LOVE this extension, but occasionally get this error: "An error occured trying to load record details: undefined" and it doesn't show me any values.

Do you know what could cause this?

Thanks!

Adam.

Adding support for LUX would be awesome.. Seems doable -at least in my non-expert eyes- since the record ID is still being used.

Per https://developer.salesforce.com/page/Workbench#Login, constructing a special URL with the sid and API endpoint embedded will auto login to force.com workbench. This seems like it would be a handy button to have.

Or does not have a record ID in the GET params of the URL. Right now clicking the schema & permissions tab does nothing if it can't find an id.

If a user is viewing a deleted record (the standard salesforce "this record has been deleted" page) then pressing the "Record Details" tab should still work by making a call to queryAll instead of query to return the full details of the deleted object.

"Uncaught TypeError: Cannot call method 'describeGlobal' of null"

Works as expected on custom objects as well as objects like Person Accounts, but when accessed from a Product2 record page, session and org details are displayed as expected - but when clicking on Record Details the following error pops up: "An error occured trying to load record details: undefined"

Otherwise excellent tool!

VF seems to have added a "i:" preamble to the base64 string. Need to strip this in pageinfo.js before base64 decoding.

When trying to use Grey tab on a SFDC record, i got an error message popping and i don't know where is the issue coming from.

The error (screenshot attached
)
says:

Error
An error occured trying to load record details: undefined

Kinda like http://www.ca-peterson.com/2012/07/force-sfdc-ui-bookmarklet.html but pretty

Selecting a SID for copy/paste use is way too annoying as-is.

Should provide non-blocking feedback to the user (i.e. not an alert() call), something like jquery UI tooltips looks promising.

Visualforce pages have a totally unique sessionId that isn't valid for API calls.

Grey Tab needs to be modified to pul in the sid cookie for the "proper" salesforce domain using the chrome.coomies API to get a valid ssessionId.

Taking a great idea from the dev console (which requires a bunch of permissons to open that you don't actually need to implement code search): implement a search across apex classes/triggers and visualforce pages/components for a specific string via SOSL.

e.g. if a new object is created after the global describe is fetched the record details tab won't work with it as it's not in the cache.

Proposal: clear the global describe is an unknown recordId prefix is found, and add a button to clear the metadata cache for the current connection to the UI.

The max salesforce session timeout is 12 hours - it makes no sense to keep inactives connections cached longer than this. While it's possible they might be valid it ends up as something of a memory leak if you access large numbers of orgs.

Proposal: include a last used timestamp on each connection and if it's >4 hrs (subject to configuration). They will be re-initialized on next use anyways, so the only penalty to this is a few extra API calls if the session was still valid.