Jump to content

jereze

Member
  • Posts

    23
  • Joined

  • Last visited

Posts posted by jereze

  1. Thanks for your answer. My bad, I thought having them in the README file on Github was enough.

     

    Screenshot:

     

    screenshot.thumb.png.7ab7e066cb2b1864b579412dd03bfed0.png

     

    Same with transparency :

    screenshot.thumb.png.3a598d888e730ad411612b53d946e64e.png

     

    Dependency:

     

    * jq

  2. Hi everyone,

     

    I have released a new version of the Salesforce workflow, 0.0.5, to address the problem with Python 2 being removed since macOS Monterey 12.3.

     

    You'll need to have Python 3 installed. It is easy to install with Xcode command line tools provided by Apple. You can find instructions here.

     

    I successfully tested it with Alfred 5.0.1 on macOS Monterey (12.5.1). Should work from Alfred 4.

     

    Best way to get the latest release is on the Github page: https://github.com/jereze/alfred-salesforce

     

    Cheers,

    Jeremy

  3. 18 hours ago, able said:

    Thank you for bringing this back! Super great workflow.

     

    I get an error message when I use it. Is it only compatible with Lightning? "Lightning Experience is enabled for your organization, but not yet for you. Want to give it a try? Ask your Salesforce admin."

     

    Hi @able,

     

    Thanks :)

     

    I guess you get an error when you open the result (in the browser).

    You can use "sf > switch" to switch the opening between Salesforce Classic and Salesforce Lightning.

     

    Cheers,

  4. Hi everyone,

     

    I have released a new version, 0.0.4, that addresses an issue introduced in the previous version.

    Also, I activated the auto-update mechanism of the workflow (for following releases).

    You can download the latest version on Github: https://github.com/jereze/alfred-salesforce

     

    @xgo: Regarding your issue, I confirm that the Salesforce App required to install the workflow is blocked by your Salesforce administrators. I also confirm that this workflow works locally; your Salesforce access or data never leave your computer when you use this workflow.

     

    Cheers,

  5. Hi everyone (and in particular @able and @jsanch01 ),

     

    I have released a new version of the Salesforce workflow, 0.0.3. It should fix the issues with Catalina.

     

    I successfully tested it with Alfred 4.1.1 on macOS Catalina (10.15.4). I believe it should work with Alfred 3+ on High Sierra and later.

    Please let me know if it works for you.

     

    Best way to get the latest release is on Github: https://github.com/jereze/alfred-salesforce

     

    Cheers,

  6. 1 hour ago, deanishe said:

     

    It's because Catalina refuses to load unsigned binaries.

     

    There is a workaround for binary executables, but AFAIK not for binary libraries like this workflow uses.

     

    The only "solution" I'm aware of would be to rewrite the workflow for Catalina and remove the problematic libraries, but as @jereze said on the previous page, the workflow requires them to work on older OSes.

     

    Hi,

    Thank you @able for reporting your issue, and thanks @deanishe for your feedback.

    I haven't upgraded my system yet to Catalina, so I cannot investigate the issue. I will try to do it by the end of November. On a technical side, I will consider switching back to Alfred-Workflow's http library or find another alternative.

  7. Hi @JJJJ,

     

    I have studied the bug report.

    No particular error during the authentication with Salesforce. I cannot explain the API error when refreshing the token (400).

    However, I found another error: No such column 'Type' on entity 'Account'.

    That's exactly the issue that got @AcidAlfred one year ago. He solved the issue making the field `Type` visible.

    Can you try to do the same?

    A next version of the workflow could fix this issue (=work without this field).

     

    On 4/27/2018 at 2:23 PM, AcidAlfred said:

    @jereze  Thanks for your help and excuse the late feedback. Indeed the "type" field in our org was hidden. After making it visible the search is now working.  

     

  8. Hello @JJJJ,

     

    I was not able to reproduce your issue.

    In the debugger output, there is not the part I'm interested in.

     

    Can you again log out and log in, then type the command "sf > debug" and send me the file (or the full content) that you will find in the directory?

    You can send it in a private message if you prefer.

     

    Jeremy

  9. 3 minutes ago, JJJJ said:

    Hello @jereze ,

     

    This workflow might be very useful for me but I get an error when I use the workflow, debugger output is below. What can I do to make it work?

     

    Starting debug for 'Salesforce'
    ...

     

    Hello @JJJJ,

     

    Glad to read that this workflow could be useful.

    In the logs, I see the following error: API error when refreshing the token (400): {"error":"invalid_grant","error_description":"expired access/refresh token"}

    Has the workflow ever worked?

    Can you try to logout and login again? (using "sf > logout" and "sf > login").

  10. @AcidAlfred Sorry for answering late. Great that the plugin now works.

    Updating fields with the plugin is possible. But which objects (leads, contacts, opportunities...) should be editable, and which of their field (only the status?)? If the plugin allows editing, it should be not too difficult to use, and generic enough so that it is useful for different people/organizations. For now I don't have enough visibility about this.

  11. 5 minutes ago, AcidAlfred said:

    Thanks for the quick responses.

     

    @deanishe Thank you for the Link

     

    @wefikus It seems like there are no restricted IPs.

     

     

    Below is the debugger output. I get the same error any time I start a "sf xxx" search. Logging in works fine.

     

     

     

     

    Here is the error: "No such column 'Type' on entity 'Account'"

    The plugin tries to get the Type on Accounts (a standard field), but Salesforce API returns an error. Do you know if the field 'Type' is available and retrievable?

  12. On 10/31/2017 at 3:41 PM, deanishe said:

    Looks useful. I have a few observations from reading the code:

     

    Is requests really necessary for this workflow? It looks like Alfred-Workflow's http library would be sufficient. The workflow's almost 20MB, and it looks like it could be under 500KB.

     

    You might also want to consider skipping logging.basicConfig(). The Workflow object initialises a "smarter" logger. It logs to a file in the workflow's cache directory (so Dropbox won't constantly be syncing the logfile in the workflow directory) and uses a RotatingFileHandler to keep the size of the logfile sane. If you use Workflow.logger, you can then also enter workflow:openlog as a query to open the log file directly.

     

    Also, you don't need to test the length of wf.args. Because you call the script with "$query" (in quotation marks) there will always be an argument, even if it's just an empty string.

     

    Thank you deanishe. BTW, your library alfred-workflow is great, thank you for the great work.

     

    In a first version, I was using Alfred-Workflow's http library but I had several Python SSL Errors. Using requests solved the issues. I thought including requests library would make the workflow more reliable across the different MacOS versions.

     

    About the logging, that's a good suggestion you make. How can I use the logger of Workflow also in server.py that starts in a new process?

     

    About the test on the length of wf.args, indeed, you are right. I will remove it.

     

  13. Hi able,

     

    Thank you very much for your feedback.

     

    Hum, I'm not able to reproduce the bug you mention. Are you typing very fast when you get wrongly the "Type at least two characters to search in Salesforce" message?

     

    About the notification: the token (ie. authorization) given by the Salesforce REST API expires after few hours. So the workflow needs to refresh the token every few hours. I should remove the notification.

     

    I will wait for more feedbacks before releasing a new version with bugfixes.

  14. Description

     

    Alfred workflow to search in Salesforce.

     

    salesforce-on-mac.gif.1f8a90f1080af17551288f87bedb703d.gif


    Keywords

     

    • `sf [blabla]` to search for any contact, account, opportunity, lead
    • `sf > login` to connect
    • `sf > logout` to log out
    • `sf > switch` to switch the opening between Salesforce Classic and Salesforce Lightning
    • `sf > debug` to write some debugs logs


    Requirements

     

    • Alfred version 3 or 4 or 5 (please see the release notes on the Github page to know which version of the workflow to use)
    • A Salesforce account with access to the REST API
    • From macOS Monterey 12.3, you'll need to install Python 3 (it is easy to install with Xcode command line tools provided by Apple, see instructions here)

     

    Resources

     

     

     

×
×
  • Create New...