#Salesforce Developers4 discussing

Recently encountered an interesting challenge related to access recovery in Salesforce Developer Orgs, and I believe it is worth discussing with the broader Salesforce community. 

In certain scenarios, when a user logs into a Salesforce Developer Org through a VPN or corporate network, the security framework may identify the activity as suspicious and automatically freeze the account. 

The challenge becomes critical when the impacted user is the only active user in the org, and the same user is also the sole System Administrator. In such cases, the Developer Org can become completely inaccessible. 

What makes this more complex is that the current support and recovery journey appears to rely heavily on authentication. Even while attempting to contact support or create a case through Agentforce, users are generally expected to log in first, which is not possible in this scenario. 

This creates a difficult recovery situation for individual developers, consultants, and small teams managing single admin Developer Orgs. 

From a platform governance and operational resilience perspective, it may be valuable to consider additional recovery mechanisms such as alternative identity verification methods, non login based support escalation options, emergency recovery workflows for single admin orgs, or clearer guidance around VPN related access restrictions and preventive measures. 

Security is absolutely essential, but equally important is having a reliable and well defined recovery path when legitimate users are unintentionally locked out. 

Curious to know: Has anyone else in the Salesforce ecosystem experienced similar situations with Developer Orgs or security triggered account freezes? 

Background: I’m designing a V1 inventory tracker in Salesforce to replace an informal spreadsheet system. We need to track physical hardware across multiple warehouses (e.g., US, International).

The Core Challenge: I need to support a Soft vs. Hard Inventory model:

• Soft: Quantity-level tracking at the Warehouse/Opportunity level for forecasting.
• Hard: Serialized tracking (Hardware Rev, Software Version) required only at the point of fulfillment.

Key Requirements:

• Inventory must decrement automatically when an Opportunity is committed.
• Device state (Serial #, Software Version) must be "locked" once delivered to ensure Support/Engineering has a clean audit trail.
• Ability to track specific versions (Rev A vs. Rev B per customer.

Current Thinking: I’m debating between a fully custom object schema (Warehouses __c, Inventory_Items __c) versus trying to leverage standard Products/Assets.

My Questions for the Group:

1. Has anyone built a similar "checkout" system? Did you use standard Assets for the "Hard Inventory" or a custom object?
2. What is your preferred logic for the "Soft-to-Hard" transition (moving from a quantity count on an Opp to a specific serial number at shipping)?
3. Any "gotchas" regarding record locking once a device is marked as delivered?

Appreciate any insights or "lessons learned" from those who have tackled hardware fulfillment! 

Hello, 

I'm not a developer but I'm trying to create custom print button for a Service Appointment list view. Unfortunately, the Service Appointment object doesn't have Printable View button. I found a code online, although, I'm getting an error: 

If someone can kindly give me some tips on the code below, I would appreciate it. Thank  you! 

<apex:page> 

<apex:page standardController="ServiceAppointment" recordSetVar="s" applyHtmlTag="false" showHeader="false" sidebar="false"> 

    <apex:slds />  

    <apex:outputPanel rendered="{!NOT(ISNULL(paramPrint))}"> 

        <script> 

            window.print(); // Triggers the print dialog 

        </script> 

    </apex:outputPanel> 

    <apex:outputPanel rendered="{!ISNULL(paramPrint)}"> 

        <div class="slds-scope"> 

            <h1 class="slds-text-heading_large">Service Appointments</h1> 

            <apex:repeat value="{!s}" var="sa"> 

                <div class="slds-box slds-m-bottom_small"> 

                    <p><b>Appointmen tNumber:</b> {!sa.AppointmentNumber}</p> 

                    <p><b>Account:</b> {!sa.AccountId}</p> 

                    <p><b>Work Type:</b> {!sa.WorkTypeId}</p> 

                    <p><b>Due Date:</b> {!sa.DueDate}</p> 

                    <p><b>Description:</b> {!sa.Description}</p> 

                    <p><b>Service Territory:</b> {!sa.ServiceTerritoryId}</p> 

                    <p><b>Address:</b> {!sa.Address} {!sa.City}</p> 

                    <p><b>Created By:</b> {!sa.CreatedById}</p> 

               </div> 

            </apex:repeat> 

        </div> 

        <!-- Button to view printable version -->  

       </apex:outputPanel> 

     <a href="/apex/PrintServiceAppointmentList?paramPrint=1" target="CarlosPMsUpcoming" class="slds-button slds-button_brand">Print This View</a> 

</apex:page> 

</apex:page> 

I'm receiving an error while trying to view a experience community page as a logged in Portal User that embeds an Omnistudio Flex Card that is built on the Omnistudio Standard Runtime Designer "Failed to process response from Apex class Exception: INVALID_TYPE: sObject type 'ApexClass' is not supported.:

".   

The data source of the Flex card is Apex Remote. This works fine when previewed by admin using test params but fails with authorized Portal Users. The same happens when a remote action is called from an Omnistudio Omniscript form for authorized portal users.  

On checking the logs in the developer tools from the browser, I saw the params are passed to the data source input, but the apex call is failed, so the flex card loads with blank data.  

The Portal User is a Customer Community Login Plus licensed, and has all the Omni related object permissions (Read), sharing settings (Public Read Only), Apex Class permissions, Field Permissions for Omni related Objects and Omnistudio Experience Cloud User Permission Set assigned. 

If any of you faced and resolved this issue before, kindly help.