HackMD - Collaborative Markdown Knowledge Base

<div> <div> <div class=""> <div class="pt-[var(--thread-visual-spacing)] md:pt-lg pb-[var(--thread-visual-spacing)] px-[var(--thread-visual-spacing)] border-subtlest ring-subtlest divide-subtlest bg-transparent"> <div class="isolate mx-auto max-w-threadContentWidth"> <div class="mx-auto max-w-threadContentWidth"> <div id="radix-:rb:-content-default" class="focus:outline-none" tabindex="0" role="tabpanel" data-state="active" data-orientation="horizontal" aria-labelledby="radix-:rb:-trigger-default"> <div class="gap-y-md mt-md flex flex-col"> <div class="grid w-full min-w-0 grid-cols-[minmax(0,1fr)]" dir="ltr" data-orientation="horizontal"> <div class="col-start-1 row-start-1"> <div id="radix-:r5s:-content-thread" class="focus:outline-none" tabindex="0" role="tabpanel" data-state="active" data-orientation="horizontal" aria-labelledby="radix-:r5s:-trigger-thread"> <div class="border-subtlest ring-subtlest divide-subtlest bg-transparent"> <div class="gap-y-md flex flex-col"> <div class="relative font-sans text-base text-foreground selection:bg-super/50 selection:text-foreground dark:selection:bg-super/10 dark:selection:text-super"> <div class="min-w-0 break-words [word-break:break-word]"> <div id="markdown-content-1" class="gap-y-md after:clear-both after:block after:content-['']" dir="auto"> <div class="my-2 first:mt-0 [&:has([data-inline-type=image])+&:has([data-inline-type=image])_[data-inline-type=image]]:hidden [&:has(table)_[data-inline-type=image]]:hidden"> <div class="relative"> <div class="prose dark:prose-invert inline leading-relaxed break-words min-w-0 [word-break:break-word] prose-strong:font-medium [&_>*:first-child]:mt-0"> <h1 class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Sage 50 Upgrade: Complete Checklist Before Updating Your Software</h1> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Planning a <strong>Sage 50 Upgrade +1-{844}-341-4437</strong> and want to avoid downtime, data loss, and frustrating error messages? A structured pre‑upgrade checklist helps your business move smoothly from an older release to the latest version, reduces the risk of “cannot find company file” issues, and keeps you ready for future updates. This guide walks through everything you should do before you <strong>upgrade Sage 50 old version to latest version</strong>, including backups, system checks, and troubleshooting common <strong>sage 50 upgrade problems</strong>.</p> <blockquote> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">For step‑by‑step help with any <a href="https://www.propertyinvesting.com/topic/5117601-sage-50-upgrade-how-to-safely-move-to-the-latest-version/#postnewtopic"><strong>sage 50 upgrade</strong></a> questions, or if you get stuck during the process, call +1-{844}-341-4437.</p> </blockquote> <h2 id="understand-your-sage-50-upgrade-path" class="mb-2 mt-4 font-display font-semimedium text-base first:mt-0 md:text-lg [hr+&]:mt-4">Understand Your Sage 50 Upgrade Path</h2> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Before you click any install button, you must clearly understand your current version and your target version for the <strong>sage 50 upgrade</strong>. Knowing whether you are moving within the same line or planning to <strong>upgrade sage 50 old version to latest version</strong> will impact compatibility, hardware needs, and testing steps.</p> <ul class="marker:text-quiet list-disc"> <li class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&>p]:pt-0 [&>p]:mb-2 [&>p]:my-0"> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Check your existing year/release from the Help > About menu so you know exactly what you are upgrading from.</p> </li> <li class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&>p]:pt-0 [&>p]:mb-2 [&>p]:my-0"> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Decide whether you are moving to the next annual release (for example, <strong>upgrade sage 50 2025 to sage 50 2026</strong>) or jumping multiple years, such as <strong>sage 50 upgrade old to latest 2024</strong>.</p> </li> </ul> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">If you are considering a platform change, like <strong>how to upgrade sage 50 to sage 200</strong>, your planning must also include data migration strategy and training. That type of upgrade is not just an installation; it is a system transition that may change workflows and reporting structures across your accounting process.</p> <h3 id="system-requirements-checklist-for-a-sage-50-upgrad" class="mb-2 mt-4 font-display font-semimedium text-base first:mt-0 md:text-lg [hr+&]:mt-4">System Requirements Checklist for a Sage 50 Upgrade</h3> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">A successful <strong>Sage 50 Upgrade</strong> begins with matching or exceeding the software’s system requirements. Underpowered workstations and outdated operating systems are a common cause of <strong>sage 50 upgrade failed</strong> messages and performance issues after installation.</p> <ul class="marker:text-quiet list-disc"> <li class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&>p]:pt-0 [&>p]:mb-2 [&>p]:my-0"> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Verify that your Windows edition, RAM, and processor meet the recommended requirements for your target version (for example, when planning to <strong>upgrade sage 50 2025 to sage 50 2026</strong> or to the latest 2024 release).</p> </li> <li class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&>p]:pt-0 [&>p]:mb-2 [&>p]:my-0"> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Confirm that all Windows updates and .NET components are fully installed and that no pending reboots are required on the workstation or server.</p> </li> </ul> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">For multi‑user environments, the server hosting the data must meet requirements before any workstation installation. Upgrading only the workstation without preparing the server often leads to <strong>sage 50 cannot find company file after upgrade</strong> errors, because the data path and program versions no longer match.</p> <h3 id="backup-strategy-before-you-upgrade-sage-50" class="mb-2 mt-4 font-display font-semimedium text-base first:mt-0 md:text-lg [hr+&]:mt-4">Backup Strategy Before You Upgrade Sage 50</h3> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Backups are the most critical step in any <strong>sage 50 upgrade</strong> checklist. You should never attempt to <strong>upgrade sage 50 old version to latest version</strong> without at least two verified backups of each active company.</p> <ul class="marker:text-quiet list-disc"> <li class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&>p]:pt-0 [&>p]:mb-2 [&>p]:my-0"> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Create a full backup from inside Sage 50 for each company and save it to an external or network location.</p> </li> <li class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&>p]:pt-0 [&>p]:mb-2 [&>p]:my-0"> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Label your backups with version and date, such as “Pre‑Upgrade‑Sage‑50‑2023‑to‑2024” so you can quickly roll back if the <strong>sage 50 upgrade failed</strong> or data appears inconsistent.</p> </li> </ul> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Consider testing a restore on a non‑production machine to confirm that your backup files are valid before starting the upgrade. If anything goes wrong—like unexpected <strong>sage 50 upgrade problems</strong> or file corruption—you can restore your data and resume operations without long downtime.</p> <h3 id="preparing-company-data-for-a-smooth-sage-50-upgrad" class="mb-2 mt-4 font-display font-semimedium text-base first:mt-0 md:text-lg [hr+&]:mt-4">Preparing Company Data for a Smooth Sage 50 Upgrade</h3> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Clean and optimized data is less likely to trigger errors during a <strong>sage 50 upgrade</strong>. Before you move to the next release, take time to tidy up your company files.</p> <ul class="marker:text-quiet list-disc"> <li class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&>p]:pt-0 [&>p]:mb-2 [&>p]:my-0"> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Run data verification and integrity checks inside Sage 50 to identify and repair minor issues before they become major <strong>sage 50 upgrade 2024 issues</strong>.</p> </li> <li class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&>p]:pt-0 [&>p]:mb-2 [&>p]:my-0"> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Archive closed years and remove obsolete test companies so the upgrade process has fewer files to process and index.</p> </li> </ul> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">When you <strong>upgrade sage 50 old version to latest version</strong>, large, cluttered datasets can make the upgrade take much longer and increase the risk of a timeout or “not responding” situation. A cleaner data environment supports faster, safer upgrading and better post‑upgrade performance.</p> <h3 id="how-to-upgrade-sage-50-accounts-core-steps" class="mb-2 mt-4 font-display font-semimedium text-base first:mt-0 md:text-lg [hr+&]:mt-4">How to Upgrade Sage 50 Accounts: Core Steps</h3> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Many users specifically search for <strong>how to upgrade sage 50 accounts</strong>, and the procedure follows a logical order that minimizes interruptions. Although the exact prompts vary by release, the structure remains similar.</p> <ul class="marker:text-quiet list-disc"> <li class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&>p]:pt-0 [&>p]:mb-2 [&>p]:my-0"> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Download the latest installer or update package for your target version, such as the release you need for <strong>sage 50 upgrade old to latest 2024</strong> or <strong>upgrade sage 50 2025 to sage 50 2026</strong>.</p> </li> <li class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&>p]:pt-0 [&>p]:mb-2 [&>p]:my-0"> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Close Sage 50 on all machines, log in as a local administrator, and run the installer, accepting prompts to upgrade the existing installation rather than creating a new path.</p> </li> </ul> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">On first launch of the upgraded program, Sage 50 typically prompts you to convert each company database to the new format. Always make sure these conversions run to 100% completion, and do not interrupt them—stopping a conversion midstream is a common reason for severe <strong>sage 50 upgrade problems</strong> and missing data.</p> <h3 id="how-to-upgrade-sage-50-to-sage-200-special-conside" class="mb-2 mt-4 font-display font-semimedium text-base first:mt-0 md:text-lg [hr+&]:mt-4">How to Upgrade Sage 50 to Sage 200: Special Considerations</h3> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">If your business has outgrown your current system and you are exploring <strong>how to upgrade sage 50 to sage 200</strong>, your checklist must expand beyond standard steps. This is not just a <strong>sage 50 upgrade</strong>; it is a move to a different product line with new architecture and capabilities.</p> <ul class="marker:text-quiet list-disc"> <li class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&>p]:pt-0 [&>p]:mb-2 [&>p]:my-0"> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Map all key data fields (customers, suppliers, nominal codes, stock, projects) so you know what will transfer automatically and what may need custom migration.</p> </li> <li class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&>p]:pt-0 [&>p]:mb-2 [&>p]:my-0"> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Identify which custom reports, layouts, or add‑ons you rely on in Sage 50 so you can plan equivalents or replacements in the Sage 200 environment.</p> </li> </ul> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Because this move involves deeper structural changes, you should plan a pilot migration in a test environment before committing fully. That allows you to identify potential <strong>sage 50 upgrade problems</strong> related to data mapping, permissions, or reporting while still having your existing system untouched for daily use.</p> <h3 id="avoiding-common-sage-50-upgrade-problems" class="mb-2 mt-4 font-display font-semimedium text-base first:mt-0 md:text-lg [hr+&]:mt-4">Avoiding Common Sage 50 Upgrade Problems</h3> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Understanding what can go wrong during a <strong>sage 50 upgrade</strong> helps you prevent those issues via your checklist. Many recurring complaints follow a simple pattern and can be mitigated with careful preparation.</p> <ul class="marker:text-quiet list-disc"> <li class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&>p]:pt-0 [&>p]:mb-2 [&>p]:my-0"> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Running the installer while Sage 50 is open on another workstation often leads to mismatched versions and can produce <strong>sage 50 upgrade failed</strong> messages or partial updates.</p> </li> <li class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&>p]:pt-0 [&>p]:mb-2 [&>p]:my-0"> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Skipping backup verification or ignoring data integrity warnings increases the risk of damaged company files and complex <strong>sage 50 upgrade problems</strong> after the process.</p> </li> </ul> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Pay special attention to third‑party integrations, custom add‑ons, and antivirus/security software. Any of these can block files, quarantine upgrade components, or alter permissions, resulting in incomplete installations and <strong>sage 50 upgrade 2024 issues</strong> that appear only when users log in after the upgrade.</p> <h3 id="fixing-sage-50-cannot-find-company-file-after-upgr" class="mb-2 mt-4 font-display font-semimedium text-base first:mt-0 md:text-lg [hr+&]:mt-4">Fixing “Sage 50 Cannot Find Company File After Upgrade”</h3> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">One of the most alarming messages users see after a <strong>sage 50 upgrade</strong> is <strong>“sage 50 cannot find company file after upgrade.”</strong> Fortunately, this is usually fixable with path corrections and version alignment.</p> <ul class="marker:text-quiet list-disc"> <li class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&>p]:pt-0 [&>p]:mb-2 [&>p]:my-0"> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Confirm the data path on the upgraded workstation and verify that it points to the correct shared or local folder where your .SAI/.SAJ or equivalent data folders are stored.</p> </li> <li class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&>p]:pt-0 [&>p]:mb-2 [&>p]:my-0"> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Ensure that the server or main machine hosting the data has also been upgraded, especially if you recently chose to <strong>upgrade sage 50 2025 to sage 50 2026</strong> or another major release.</p> </li> </ul> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">If the program opens but lists no companies, you may just need to re‑browse and re‑attach to the existing company folders. In severe cases where the data conversion did not complete, restoring from your verified pre‑upgrade backup may be the safest option, particularly when facing repeated <strong>sage 50 upgrade failed</strong> errors on the same file.</p> <h3 id="troubleshooting-sage-50-upgrade-failed-messages" class="mb-2 mt-4 font-display font-semimedium text-base first:mt-0 md:text-lg [hr+&]:mt-4">Troubleshooting Sage 50 Upgrade Failed Messages</h3> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">When you see a <strong>sage 50 upgrade failed</strong> notification, the key is to collect as much information as possible rather than repeatedly re‑running the installer blindly. Each failure provides clues you can use to refine your checklist.</p> <ul class="marker:text-quiet list-disc"> <li class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&>p]:pt-0 [&>p]:mb-2 [&>p]:my-0"> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Note any specific error codes, missing components, or file access warnings so you can resolve the root cause before your next upgrade attempt.</p> </li> <li class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&>p]:pt-0 [&>p]:mb-2 [&>p]:my-0"> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Check permissions for both the installer and the data directories; lack of full control or security software blocking operations often contributes to <strong>sage 50 upgrade problems</strong> and partial installations.</p> </li> </ul> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">After addressing the cause, you can re‑run the upgrade, and then immediately test launching your companies to ensure there are no <strong>sage 50 upgrade 2024 issues</strong> or login errors remaining. Keeping a log of what you changed and tested will also help if you later need expert assistance.</p> <h3 id="postupgrade-checks-after-a-sage-50-upgrade" class="mb-2 mt-4 font-display font-semimedium text-base first:mt-0 md:text-lg [hr+&]:mt-4">Post‑Upgrade Checks After a Sage 50 Upgrade</h3> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Once your <strong>Sage 50 Upgrade</strong> completes successfully, the process is not finished until you verify that daily operations work as expected. A post‑upgrade test plan will help you confirm that everything from login to reporting is functioning properly.</p> <ul class="marker:text-quiet list-disc"> <li class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&>p]:pt-0 [&>p]:mb-2 [&>p]:my-0"> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Log into each company, run key reports, and test essential workflows such as posting invoices, receipts, bank reconciliations, and period‑end processes.</p> </li> <li class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&>p]:pt-0 [&>p]:mb-2 [&>p]:my-0"> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Confirm that all workstations connect without “company not found” errors and that user permissions, audit trails, and reference numbers behave normally after you <strong>upgrade sage 50 old version to latest version</strong>.</p> </li> </ul> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">If you recently performed an <strong>upgrade sage 50 2025 to sage 50 2026</strong> or a <strong>sage 50 upgrade old to latest 2024</strong>, verify that new features or compliance changes are applied correctly and that your reports reflect the expected fields and layout. Early detection of anomalies makes them easier to fix while your backups and notes are still fresh.</p> <h3 id="when-to-get-expert-help-with-sage-50-upgrade-issue" class="mb-2 mt-4 font-display font-semimedium text-base first:mt-0 md:text-lg [hr+&]:mt-4">When to Get Expert Help with Sage 50 Upgrade Issues</h3> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Even the most carefully planned <strong>sage 50 upgrade</strong> can run into unexpected obstacles, particularly in complex networks, older environments, or heavily customized setups. Recognizing when to call for help can prevent extended downtime and data damage.</p> <ul class="marker:text-quiet list-disc"> <li class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&>p]:pt-0 [&>p]:mb-2 [&>p]:my-0"> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">If you repeatedly encounter <strong>sage 50 upgrade failed</strong> messages, cannot resolve <strong>sage 50 cannot find company file after upgrade</strong>, or see unusual data behavior, it is safer to pause and seek guidance.</p> </li> <li class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&>p]:pt-0 [&>p]:mb-2 [&>p]:my-0"> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">Businesses migrating from older releases through multiple steps, such as <strong>sage 50 upgrade old to latest 2024</strong> while also changing hardware or servers, often benefit from expert review of their upgrade plan.</p> </li> </ul> <p class="my-2 [&+p]:mt-4 [&_strong:has(+br)]:inline-block [&_strong:has(+br)]:pb-2">For personalized guidance, troubleshooting, and hands‑on support with <strong>how to upgrade sage 50</strong>, <strong>how to upgrade sage 50 accounts</strong>, or resolving <strong>sage 50 upgrade problems</strong>, call <strong>Sage 50 Upgrade +1-{844}-341-4437</strong> to get help tailored to your exact version, environment, and business needs.</p> </div> </div> </div> </div> </div> </div> <div class="flex items-center justify-between"> </div> </div> </div> </div> </div> </div> <div class="gap-y-lg flex flex-col first:mt-0"> </div> </div> </div> </div> </div> </div> </div> </div> </div> <div> <div> <div class="erp-sidecar:min-h-[var(--sidecar-content-height)] erp-mobile-sidecar:min-h-[var(--mobile-sidecar-content-height)] min-h-[var(--page-content-height)]"> <div class="pt-[var(--thread-visual-spacing)] md:pt-lg pb-[var(--thread-visual-spacing)] px-[var(--thread-visual-spacing)] border-subtlest ring-subtlest divide-subtlest bg-transparent"> <div class="isolate mx-auto max-w-threadContentWidth"> <div class="bg-base erp-sidecar:pt-0 erp-mobile-sidecar:pt-0"> <div class="mx-auto max-w-threadContentWidth"> <div class="max-w-threadContentWidth relative isolate z-20 mx-auto"> <div class="relative z-10"> <div class="group relative flex items-end gap-0.5"> <div class="relative min-w-0 flex-1 flex justify-end"> <div class="flex items-center gap-2"> <div class="flex shrink-0 items-center gap-1 opacity-0 transition-opacity duration-150 pointer-events-none group-hover:pointer-events-auto group-hover:opacity-100 focus-within:pointer-events-auto focus-within:opacity-100" aria-hidden="false"> </div> <div class="group/title relative inline-flex flex-col"> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div> </div>