Forum Widgets
Latest Discussions
PivotTable Date Slicer Not Visible in Excel for the Web (Works in Desktop)
Hi everyone, I'm experiencing an issue with Excel for the web and was hoping to get some help. I have an Excel workbook that is linked to a 'Microsoft Forms' form. The form responses automatically populate the main sheet, and from that data I've created several PivotTables. In one of the PivotTables, I added a date slicer to filter the data. Everything was working fine at first, but recently the slicer is no longer visible in Excel for the web. However, when I open the same workbook in Excel Desktop, the slicer is visible and it works as expected. What I have tried so far: Recreating the PivotTable and adding a new slicer Creating a completely new PivotTable and slicer Checked if the slicer is hidden by adjusting the zoom Unfortunately, the issue persists in Excel for the web. Has anyone experienced this before and found a workaround? Any help would be appreciated. Thanks in advance.
Managing Blank Cells in multiple linear regression analysis.
Hello, I am performing a multiple linear regression analysis using the Analysis Toolpak in Excel 365. I have complete y-data, but the x variables are missing some data points throughout a large data set. I know I can fill in the data with the mean or potentially use a regression analysis to predict data to fill in the blanks; however, I would prefer to ignore the blank data if possible. Is there a way to do this inside the data toolpak?
Excel: Subtract multiple parts from inventory with a single input
Ho un sistema di inventario in Excel con tre tabelle: Elenco principale di tutti i ricambi (Codice ricambio, Voce, Usato, Magazzino) Registrazione delle parti in entrata Registri UTILIZZATI delle parti consumate Il sistema funziona bene quando consumo singoli componenti , dato che mi basta inserire il codice del componente nella tabella UTILIZZATI e aggiornare le scorte. Il problema si presenta quando utilizzo dei componenti nell'ambito di un processo. Per esempio: Un Gruppo1 utilizza più parti Un assemblaggio completo utilizza tutte le parti Al momento, se completo un gruppo o un intero assemblaggio, devo inserire manualmente ogni singolo componente nella tabella USED. Vorrei poter inserire un singolo riferimento nella tabella USED (ad esempio: Gruppo1 o Completo) e far sì che Excel lo calcoli automaticamente: dedurre tutte le parti correlate dalla tabella PARTI basato su una mappatura predefinita La mia idea è quella di creare una tabella di mappatura (simile a una distinta base/definizione di gruppo), in cui ogni gruppo sia collegato a più codici articolo con una quantità definita per articolo. Quindi, quando inserisco un gruppo nella tabella USED, Excel dovrebbe sottrarre di conseguenza tutte le parti associate. La domanda è: come posso farlo?
Office Scripts
i have a business microsoft office account and am signed in with it. when i try running a script in excel i keep getting the error saying it requires a work or school account. my microsoft account says the following: your work or school account belongs to your home organisation. what do i need to do to get scripts working.
Pivot Table TOP 5 vs Slicer
I create a Pivot Table, sort the data then filter on the TOP 5. I then create the Pivot Chart (horizontal TOP 5 bar chart). In my dashboard, I have slicers. When a Slicer filter is applied then removed, the Pivot Table and Chart do not go back to display the TOP 5 data but the whole set of data. Any simple way to ensure the pivot table / Chart recovers only the TOP 5 values (and not the whole set of values) after the slicer filters are reset ?
Getting started in Excel Labs Custom Modules (missing "publish" step)
First-time poster — please be gentle! Context Excel for Mac I have a large library of LAMBDA formulas and wanted to manage them using Excel Labs In particular, I wanted to organise formulas into custom Modules Issue How to actually activate functions defined in custom Modules in Excel Labs I recently discovered Excel Labs and was very excited to use it to manage and structure a large library of LAMBDA formulas. My goal was straightforward: create custom Modules to organise formulas by purpose, and then use those formulas in the workbook. However, it took several hours of experimentation and debugging — even to get a trivial example like: ABC() = 12 to work when defined in a custom Module. The missing piece (which Copilot, Google searches, and the README all missed) is this: Functions defined in custom Excel Labs Modules are inert until the module is imported into the special Workbook module. Until that import step occurs, functions in custom Modules: do not appear in Excel Labs → Names do not appear in Formulas → Name Manager are not callable from the grid According to Copilot this behaviour is not currently documented, and the UI strongly suggests that custom Modules are “active” by default — which they are not. Working workflow (for others who hit the same issue) This is the workflow that finally made things work for me (possibly sub‑optimal, but reliable): Create and maintain functions in custom modules (e.g. Transformations) Explicitly import the required functions into the Workbook module, e.g.: TransformAtoB = Transformations.TransformAtoB Workbook module now publishes to: Excel Labs → Names Formulas → Name Manager This makes conceptual sense — maintain a large structured library of formulas (or import libraries from GitHub), only activate the formulas required by a particular workbook. But without documentation, it’s very easy to assume custom Modules are active by default. Why I’m posting this When I finally asked Copilot “Why didn’t you say this up front?”, the answer was essentially: This publish step is not documented in the README or the UI, and users are easily led to assume Modules are active by default. So I’m posting here to save others from repeating the same debugging journey. Documentation request It would help enormously if the documentation (README / FAQ) stated explicitly that: Custom Modules are source-only Importing into the Workbook module is the publish step Only the Workbook module is wired to Name Manager and the Excel grid Even a short note would remove a major stumbling block for new users. I’m not a GitHub user, otherwise I would also raise this there — if someone from the community is able to mirror this feedback on GitHub, that would be much appreciated.Excel Macros Spreadsheets Not Loading
I've spent some time with Microsoft Support (almost 3 hours, including uninstalling my MS 365 and reinstalling it), but I'm having an issue with my Excel Macro spreadsheets not loading at all. This is what I get each time. Also having an issue with non-Macro spreadsheets that I'm unable to use the Bold, Italic, and Underline functions (get the spinning wheel and then Excel Not Responding), as well as not able to use the Format function (get the same spinning wheel and then Excel Not Responding). I've been using these same Excel Macro Spreadsheets for over 15 years. Please help!A 40,000+ VBA line Block and Stack workplace planning tool made in Excel
Hi all, I’ve been an Excel user for a long time, but until the last 8 months I had never really explored the full power of Excel/VBA. With AI’s help, I’ve been building a workplace Block and Stack planning tool called Work Stack. It’s a niche use case, but a very real one in my industry, supporting corporate office planners, workplace teams, and anyone trying to move and reorganise teams within an office. When I first started, I thought an AI agent would simply be able to generate the answer for me. I quickly realised that wasn’t enough, especially when it came to reliably recreating the block and stack image and handling the planning logic behind it. That was when I decided to build it properly. I have zero coding background, but 15+ years of workplace experience, so the setup became: AI as the code developer, and me as the product owner, logic lead, tester, and relentless breaker of whatever had just been built. I moved very quickly at first and had a “working model” within about 6 weeks. The problem was that it produced all sorts of crazy results and was basically unusable, untestable, and unfixable. That was where I learned some hard lessons about relying too heavily on arrays and not being disciplined enough with separation of concerns. Version 1 was a false start, but a very useful one. I scrapped it and rebuilt the tool properly from scratch. The rebuild took 6+ months rather than 6 weeks, but Work Stack is now at beta stage and is being tested and demoed by industry peers. Attached are 3 images: Image 1 — Current Stack This is a standard desk-sharing workplace stack. It shows teams grouped into functions, some placed in neighbourhood zones, some co-located with other teams (shown with the two-headed arrow), and some “breached” teams shown with a red border where they are sharing desks more aggressively than the building guideline allows (80% in this example). There are also scattered spare desks shown in white blocks at the end of floors. As teams move, the team blocks, floors, and footer totals all recalculate automatically. Image 2 — AutoStack Output This is the result of running the most complex feature in the tool: AutoStack. It assesses the current stack and then restructures it based on the user’s instructions. In this example, I asked it to fix all breached teams, reunite teams with their function groups, dissolve neighbourhood zones and co-locations, and consolidate spare desks where possible. Something that would normally take a space planner weeks of effort can now be done by VBA in Excel in seconds. That part still blows me away. Image 3 — Stack Editor This is the main parent form, called Stack Editor. It acts as the control hub for creating, editing, and customising the stack. At the moment it has 37 features and counting. Under the hood, the rebuilt version is structured far more seriously than the original. It uses an object-oriented VBA model built around core class modules for the plan, floors, and teams, with supporting classes for things like zones, functions, financials, and rendering. In other words, the stack is modelled as real objects rather than just spreadsheet rows. I also rebuilt it with much stricter boundaries between logic, persistence, rendering, and UI. That discipline is what made the second version stable enough to keep growing, and it is a big part of why the codebase has now grown to 40,000+ lines without collapsing under its own weight. I mainly wanted to share this with people who might appreciate this very specific use case in VBA. At some point I may need to port it to Python or something similar, but for now I’m honestly amazed at how far this 30-year-old language can be pushed.
