-
Recently active
I Installed Box for Salesforce and Use Apex Action「Get Folder ID By Record ID」 by Flow. But I get an Error mail everytime. From: FlowApplication <info@jp.salesforce.com> Date: ***** Subject: フロー「Target Folder Under Account」でエラーが発生しました: An Apex error occurred: box.Toolkit.BoxApiException: エラー要素 boxID_Parent (FlowActionCall)。 An Apex error occurred: box.Toolkit.BoxApiException: I don’t know what a happen. Error mail has no Detail Information.(ex. Missing required input parameter: recordId. ) In ApexDebugLogDetail, I can’t get an error information too. 14:06:45.229 (229451568)|HEAP_ALLOCATE|[EXTERNAL]|Bytes:8 14:06:45.229 (229480913)|VARIABLE_SCOPE_BEGIN|[31]|this|box.GetFolderIdByRecordId_v2.Request|true|false 14:06:45.229 (229546908)|VARIABLE_ASSIGNMENT|[31]|this|{}|0x5562b465 14:06:45.229 (229624678)|HEAP_ALLOCATE|[EXTERNAL]|Bytes:4 14:06:45.229 (229630570)|HEAP_ALLOCATE|[EXTERNAL]|Bytes:8 14:06:45.229 (229741110)|VARIABLE_ASSIGNMENT|[EXTERNAL]|this.recordId|“0015j00001DOKzrAA
Is there a flow bulk pattern for creating Box Folders with default batch size of 200. When I insert 200 custom object records, I want 200 box folders created. Reducing batch size works, but not ideal. In the debug logs I see multiple SOQL queries executed by the Box managed package for a single Folder create which ends up tripping the salesforce limits - An Apex error occurred: System.LimitException: box:Too many SOQL queries: 101
when I run flow to create a folder for a couple of records (using data loader to update the records to meet the criteria) I get this error “Error Occurred: An Apex error occurred: box.Toolkit.BoxApiException: Unable to create a folder for record id 5002M00001ZXLc4QAH - Details: The folder was returned with a null id.” however when I go to this record and updated to meet the criteria to trigger the flow the folder gets created without any issue any idea why I get this issue? the flow run Asynchronously using BOX Apex “create folder”
This is happening only when the record doesn’t have a folder created but once the folder gets created the message will be gone this is very inconvenience for the users, is there a way to prevent it from showing up also, this is only happening with content explorer component
Hey all, sorry if this question has been asked before, I couldn’t find anything with a search. We are currently using the box SDK for salesforce and we are trying to insert around 5 subfolders and 1 root folder in one transaction. Currently we are using single call outs for ever folder but are wondering if there is a way we could use 1 call to create multiple folders. I haven’t found any documentation for anything other than single folder creation in both the SDK and the toolkit documentation. I was wondering if there are any solutions to this or if we only get the single call out for folder creation? Thanks!
Box now connects content workflows between Salesforce and Slack with a new Salesforce Developer Toolkit feature, details here Join for a live demo at our Community Roundtable next week. Box for Salesforce Community Roundtable
I wanted to answer a question from one of our Community Roundtable members @NLeo here in the forums so that others may benefit from the approach. Question from @NLeo: How can we load Content Explorer and Content Uploader UI Elements in Experience Cloud? Here are you current options: Wait a few weeks until our team releases UI Elements for Experience Cloud within our managed package. You can leverage a screenflow and drag and drop the existing Ltn components within a screen. The downside to this approach is that you’ll need to run the screenflow as the Box service account and will not show up the Experience/Community user performing the Box actions. I have an open source community project that can be modified for your specific use case. I would treat this as a starter and by no means as production-ready unmanaged package: https://github.com/kylefernandadams/box-ui-elements-lwc If your timelines are flexible Option 1 is the obvious choice. Option 2 isn’t my favorite, but if you
Hello Everyone, Yesterday I preparing to deploy Box to Salesforce Prod After the installation was done I kept getting an error from Box flow “Assign Box Permissions” Error element Create_Permission_Set_Assignments (FlowRecordCreate). This error occurred when the flow tried to create records: FIELD_INTEGRITY_EXCEPTION: The user license doesn’t allow Assigned Apps. You can look up ExceptionCode values in the SOAP API Developer Guide. any idea what happening I had to deactivate the flow
Any tips for testing Box integrations that are used in apex? I’m not sure whether it’s better to Surround all Box methods/auth/api calls in apex with if(!Test.isRunningTest()) so that those lines of code are skipped? Create mock HTTP responses to be able to step through the lines of code if a test is running? eg. HttpResponse response = Test.isRunningTest() ? new Http().send(request) : toolkit.sendRequest(request); Something better? I can see #2 perhaps being best practice, however we use many different box methods (createFolder(), createFolderForRecordId(), commitChanges(), moveFolder(), getFolderByRecordId(), etc) and this could be very tedious to create custom responses for each one. Thoughts?
Please find attached a recording, summary and resources from our most recent Box for Salesforce roundtable here We would like to express our gratitude to Don Hammons of mxHero, Kyle Adams, and Shawn Shay from Box for their excellent presentations. We also extend our thanks to the guests who joined us. Highlights. Recording here Overview of Box automations available in Salesforce Demo of Box Sign for Salesforce mxHero Overview of email management from the cloud and demo of Mail2Sign mxHero LLM AI integration with Mail2BoxSign Box Sign Roadmap (21 CFR Part 11 Compliance, and other updates coming soon)
We are currently implementing a functionality to automatically create a Box folder upon record creation in Salesforce. However, we are facing an issue where the folder creation process does not occur (no folder is created, and the return value is NULL) when using the createFolderForRecordId method from the Salesforce Developer Toolkit within an after insert trigger on record creation. We have confirmed that the process works correctly and the folder is created when manually triggered from the Developer Console. Could you please provide guidance on the possible cause of this issue? If it is not possible to achieve automatic folder creation within the trigger, could you please suggest an alternative solution for resolving this requirement? I got a error message as below. 18:18:41:463 USER_DEBUG [572]|DEBUG|Unable to create folder for record id a0E1m000007S0gcEAC - Details: Unable to use default credentials to make a callout to Box (maybe this is in a trigger, constructor, or after a DML
Could you please provide guidance on how to use the API (Update metadata instance on folder:PUT) using Apex? For Create metadata instance on folder(POST), I was able to achieve it as described above. However, I’m unsure how to set the Body for Update metadata instance on folder. Sample Code for Use Create metadata instance on folder(POST) box.Toolkit toolkit = new box.Toolkit(); String folderId = project.ProjectFolderId__c; Map<String, String> metadata = new Map<String, String>{ ‘masterdefkeyword1’ => project.Keyword1__c, ‘masterdefkeyword2’ => project.Keyword2__c, ‘masterdefkeyword3’ => project.Keyword3__c, ‘projectsupplementkeyword1’ => project.SupplementKeyword1__c, ‘projectsupplementkeyword2’ => project.SupplementKeyword2__c, ‘projectsupplementkeyword3’ => project.SupplementKeyword3__c }; String scope = ‘enterprise’; String tempName = ‘projectmetadatatemplate’; // Box endpoint(Create metadata instance on folder) String endpoint
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.