-
Recently active
Building your own managed package? Got Apex on your mind. Here’s your spot. For more information, you can check out these links: Docs page Github home Github docs Sample Code
I realize this is probably the wrong forum. And I am sure I am overlooking something simple - but I am having an issue with new users view of folders within Box. I haven’t had this problem in the 2+ years we have been using Box and I have spent more time than I care to admit trying to figure it out. For the last two years my existing users will navigate to the folders in Box via the path - All Files>Salesforce Root Folder>Object Folder>Record Folder. All collaboration is granted via the Box for Salesforce integration. They don’t have collaboration rights granted to anything but the selected Record Folders - but they are housed in the above tree and makes their All Files page much cleaner. The issue is that my recent new users (last 2 months) are not getting this same tree. Instead it is All Files>Record Folder. And results in a cluttered mess on their All Files page. Ultimately they can still get the folders and files they need to do their job - but the user experience isn’t great. Out
Hello, new member here. I have a question concerning the connection to Salesforce. I asked the Admin of our account to make my account a co-admin with all the rights to connect Box to Salesforce but the admin is getting an error that indicated nothing. Just Impossible to modify user. Does anyone have a Lead or a Box contact I can get help from ? Thanks
When certain conditions are met, I need to Move a box folder to a different Object and Record ID association. What is the best way to do this? I have access to both the Salesforce SDK and developer toolkit. Should i just update the box_FRUP__c object? I dont see a method for changing association, so it looks like I may need to move the folder to the Opportunity root, then change the FRUP association? I tried this though and BOX doesn’t like it. Maybe I’m doing it wrong.I have tried a few things but, its not quite working correctly: I call these two methods in a Queueable context method post conversion. public static void moveFolder(Id currentRecordId, Id destinationRecordId){ box.Toolkit toolkit = new box.Toolkit(); String currentFolderId = getRecordFolder(currentRecordId); String destinationObjectId = getObjectFolder(destinationRecordId); toolkit.moveFolder(currentFolderId, destinationObjectId, null); toolkit.commitChanges(); } public static void changeFolderAssociation(Id changeRecor
Hi, I’m running an API Call to upload a PDF file to Box. I get the PDF URL from another API call to another software, and then input the URL into this apex class, it downloads it and uploads it into Box folder of specific folder Id which I input. For some reason, everything works, but the file that comes into Box is not PDF and is of unsupported file type (can’t be opened or downloaded). Can anyone find what my error could possibly be? public class HV_BoxPDFUploader { @InvocableMethod(label='Upload PDF to Box' description='Uploads a PDF from a URL to Box using Box Toolkit') public static List<Result> uploadPDFToBox(List<Request> requests) { List<Result> results = new List<Result>(); for (Request req : requests) { Result res = new Result(); try { // Download PDF content Http http = new Http(); HttpRequest pdfRequest = new HttpRequest(); pdfRequest.setEndpoint(req.pdfUrl); pdfRequest.setMethod('GET'); HttpResponse pdfResponse = http.send(pdfRequest); if (pdfResponse.getStatusCode() == 20
System.HttpRequest[Endpoint=https://api.box.com/2.0/files/####/, Method=GET when calling above api we are getting this error. System.CalloutException: arraycopy: last source index 32 out of bounds for byte[31] We seem to be getting this error periodically at random intervals. I removed the number in the endpoint and replaced it with #### for the sake of this post.
We are creating a folder via a flow, when we debug, we get the following error: An Apex error occurred: box.Toolkit.BoxApiException: The folder was returned with a null id. When we debug, it appears the folder id exists to be passed. Any advice?
Hi, We are trying to add a custom UI using the Box Content Explorer javascript library from the UI Elements SDK. The Box Content Explorer requires an auth token to authenticate. This must be the Salesforce user rather than a service account in our case so security and access is respected. There does not appear to be a method to retrieve a user's auth token from the Salesforce toolkit. Looking outside the toolkit to the Salesforce SDK, there isn't an implementation of the OAuth user flow (this must be implemented by the application) and my understanding is that this would be an additional log in to the Box for Salesforce login. I'm currently looking into using the toolkit to query a Box managed user's Id using the username from Salesforce and then getting a user token through a Client Credentials custom app. What is the best way to seamlessly integrate the Box for Salesforce toolkit with the Box UI Elements SDK so that there is a single authentication process? Thanks
Hello, We are trying to bulk create Box folder/subfolders for existing Person Accounts in Salesforce. We have different Record Types available in Salesforce and our Box folder structure will be slightly different for each of those Record Types. Is there any way we can bulk create these folders in Box without consuming too many API callouts? Thanks Deepak
Need advice on how to pull from salesforce to box without file size limitation
Box and Salesforce integration using Box for Salesforce. When you create a record in Salesforce using Box for Salesforce, a folder is created on the Box side. If you do not reference the Salesforce record at this time, the user will not be granted privileges to the Box folder. Therefore, even if a folder is created, most users will have to go to Salesforce to see the corresponding record in order to access the folder. Is there a better way to grant privileges without access to the records? I tried Box tool kit createCollaboration and https://api.box.com/2.0/collaborations, but this one did not create a FRUP record and the Box for Salesforce delete batch did not work properly.
Hi Team, I am using Box Toolkit for Salesforce; I have authenticated one service account. But I don’t want add user account in user settings as we are having users in large number. So, we can’t add users every time. Is there any other way of using Box Toolkit to upload files on box folder without providing user account? Thanks Jahanvi
Hi, I have a requirement where, once an object is updated from an external system, a process is triggered that will fetch all the files from the updated object and save the files into a specified box folder into another object that is newly created. I have used the Box toolkit method - createFileFromAttachment() to add the files to the new folder. The method is also getting executed in the future context and callouts are allowed. Yet the process throws an authentication error that starts with: "boxtoolkitToolkit:[AUTH_WRAPPER_PREPARE_FAIL_MESSAGE=Unable to use default credentials to make a callout to Box (maybe this is in a trigger, constructor, or after a DML statement):, authWrapper=BoxAuthWrapper:[adminSettings=box__BoxUser_Settings__c:{}, " Once the process gets executed, if multiple files need to be transferred, only one file gets transferred to the destination folder, and the other files are stopped after the same error is encountered. I’m implementing the requirement in Salesfor
Hi, We would like to implement a flow to delete folder after 30 days of case being closed. Support have advised we should use the Send Request Action in a flow however it isn’t visible to us, any ideas why this may be? We are using Version 4.28 Thank you
We are integrating using SF and would like to assign a zone to files depending on the region on the account record. Does anyone have any suggestions on how we can achieve this using SF flow? Thank you
When trying to add Salesforce UI Elements into Lightning Page or Flow - I am seeing this error when opening page or running the flow Refused to frame 'https://mydomain--mysandbox-box.sandbox.vf.force.com/' because an ancestor violates the following Content Security Policy directives: "frame-ancestor 'self'" Additional Info: https://developer.box.com/guides/tooling/salesforce-toolkit/ui-elements/
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|“0015j00001DOKzrAAH”|0x5562
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 don’t hav
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?
9 likes
8 likes
4 likes
3 likes
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
