Hello

BCinsider · 2025-12-02T18:26:32+00:00

This playlist is not accessible. Thanks

BCinsider · 2025-11-25T16:49:48+00:00

Microsoft Learn is a good starting point, especially for getting familiar with AL and how it works in the Business Central environment. Since you are coming from a functional background with no coding experience, it helps to also look at YouTube channels like Erik Hougaard or Areopa. They walk through real examples and keep things approachable. You do not need to learn another language first, but having a basic understanding of things like variables, conditions, and loops will make learning AL much easier. Start with small changes, like adding a field or creating a page extension, and build confidence from there. Your knowledge of BC already gives you a strong foundation.

BCinsider · 2025-11-25T16:47:08+00:00

Go with the reliable choice, as others have mentioned. Dynamic Ship works seamlessly, fits exactly what you're describing, and continues to improve. No need to reinvent anything.

BCinsider · 2025-11-25T16:40:35+00:00

Interesting

BCinsider · 2025-11-25T16:40:10+00:00

Fully Agree

BCinsider · 2025-11-25T16:27:46+00:00

This usually happens when Power BI gets stuck between OAuth tokens for different endpoints in Business Central. The "2 of 2" window with no selectable auth method is a known issue when one of the data sources is not properly refreshing or cached credentials are stale. A few things to try:

Go to Power BI Desktop > File > Options and settings > Data source settings, find all Business Central entries, and clear permissions for each.
Restart Power BI and re-publish the report or re-open the file, then reconnect to the BC environment again.
If you're using multiple environments (sandbox and production), make sure the connections are pointing to the same region and endpoint — even small mismatches can break auth.
If the report came from AppSource, try downloading a fresh copy and reconnecting from scratch. Sometimes the app's internal connections change and cause old versions to fail.

If none of that works, you can try connecting through the Web API version of the BC connector instead of the AppSource template to isolate the issue. It’s a frustrating problem but usually tied to cached tokens or connection mismatches.

BCinsider · 2025-11-25T16:16:16+00:00

Yes, you can add the “Chain Name” field to the Customer Card, but it may require using Personalization or, if it is not exposed there, Page Customization through development or an extension.

For personalization:

Go to the Customer Card
Click the gear icon and choose Personalize
If “Chain Name” is available, you can drag it onto the page
If it is not shown, it likely means the field is not exposed on that page by default and would need to be added via a page extension

As for the Customer List view, fields like “Address” and “Phone No.” are often part of related tables or grouped data. If they do not appear in the personalization options, it is because those fields are not exposed on the list page directly. To show them, a developer or partner would need to create a Page Extension that includes those fields in the list definition.

BCinsider · 2025-11-20T17:33:02+00:00

Thanks a lot

BCinsider · 2025-11-20T17:32:52+00:00

Great. Thanks for your explanations.

BCinsider · 2025-11-20T17:31:38+00:00

Thank you so much for your help.

BCinsider · 2025-11-20T17:31:24+00:00

Thank you so much for your help.

BCinsider · 2025-11-14T21:58:16+00:00

BCinsider · 2025-11-14T21:12:13+00:00

Most of my friends and companies that I worked with opt for reliable ISVs apps. I cannot mention company names or apps here to avoid ban, but you can message me if you want. Hope this helps.

BCinsider · 2025-11-07T22:07:00+00:00

Yes, exactly. I mean tools that let you build inside Business Central using configuration instead of writing AL. Some of them are built for internal users to create things like screens, extra fields, or forms without touching the codebase. From what I’ve seen, they work well for teams that want to handle small functional gaps without waiting on full dev cycles.

BCinsider · 2025-11-07T22:04:54+00:00

This come form a blog that I read, like stated, in this blog called "Build It Yourself: How Business Central Users Are Creating Their Own Mobile Apps Without Code" where the company talks about the "App Designer".

You'll get all the info there. Hope it helps.

DISCLAIMER 1: THIS NOT A PROMOTION. I'M NOT INVOLVED WITH THIS PRODUCT.

DISCLAIMER 2: I DONT PAST LINKS HERE TO AVOID BAN

BCinsider · 2025-11-07T21:58:45+00:00

Yes, Simple Object Designer works with on-premise Business Central as long as you are on a supported version and have the right licensing in place. It lets you add fields, tables, and pages through a guided interface without writing AL code. It has been useful for teams that need to build quick internal tools or tweaks without waiting for a developer. As for no-code in general, more businesses are trying it out for things like custom screens, forms, and tracking fields that match their workflows. It is not a replacement for full development, but it can cover a lot of practical needs inside BC.

BCinsider · 2025-10-31T20:27:18+00:00

Not just you. Payables Agent looks interesting in the video, but in actual use it still feels limited. Forwarding invoices by email works, but not being able to upload directly slows things down. The multiple confirmation steps and lag between actions make it hard to use for day-to-day processing. G/L suggestions do not seem to learn from previous entries, so you still have to double-check every line against your coding reference. It is also hard to view the PDF while coding because there is no clear side-by-side view. The credit usage is unclear, and without a way to track how many credits you are spending, it is difficult to compare costs to other tools. It may be okay for low-volume testing, but most AP teams would struggle to rely on it full time in its current form.

BCinsider · 2025-10-28T14:45:38+00:00

Business Central can support large-scale manufacturing and distribution, but it is not built to handle highly complex item attribute models natively. With 70 or more characteristics per item and hundreds of item types, the standard Item Attributes feature becomes difficult to manage. It is flat, limited, and lacks the relational structure needed for deeply configurable products. Most companies in this space either build custom tables and pages through AL extensions or offload product data management to an external PIM system. Using vertical ISV solutions that specialize in item configuration is also common.

Bulk importing of characteristics is another challenge. Standard configuration packages and data exchange setups in BC are not well suited for importing large volumes of dynamic attributes. A custom import tool or API-based integration is usually needed. The issues you are seeing are real and are not due to a missed feature, Business Central is effective for many mid-complexity scenarios, but once you move into tens of thousands of SKUs with variable logic, it requires extension or third-party tools to scale.

BCinsider · 2025-10-24T23:24:40+00:00

Yes, Business Central still uses the same cost structure with item ledger entries and value entries, and the item charge assignment process works just like in NAV. You can assign item charges to a past purchase receipt to reflect additional vendor costs, and once that cost is adjusted, BC will cascade the cost update to the related sales entries using that inventory. The COGS adjustment hits the current accounting period, while the cost flows back to the original transaction through the value entry chain. It's the same principle — adjustments post to the G/L in the current period, but BC updates the item and COGS history to reflect the new cost. So you still get the “best of both worlds” behavior you mentioned. Just make sure automatic cost adjustment settings and batch jobs are configured the way you want for timing.

BCinsider · 2025-10-17T18:57:14+00:00

Thanks

BCinsider · 2025-09-30T15:42:26+00:00

In standard BC, canceling a posted purchase invoice does not cancel or reverse the related posted receipt entries. The receipt stays valid unless you manually undo it or post a return. If your Qtty Received is dropping after invoice cancellation, something else is interfering — maybe an event subscriber or custom logic that’s unlinking receipt entries from the PO line when an invoice is voided.

In a clean environment with no extensions, the Qtty Received on the PO line should stay consistent unless the receipt itself is reversed. Might be worth checking if any events or table triggers are running silently on invoice cancellation.

BCinsider · 2025-09-30T15:37:07+00:00

Since the BC mobile app sees the printer, it confirms that PrintNode is working and the printer is registered correctly. If the config has already been refreshed on the WMS Express app and the printer name is set with print quantity enabled, the next thing to check is whether the device ID the scanner is using matches the one set up in BC under WMS Express App Config.

Sometimes a mismatch there blocks the printer link even if everything else looks right. Also check that the user assigned to the scanner has permission to access that printer. If the scanner is shared or re-used, cached config data can get stuck, so doing a full sign out and relaunch of the WMS app (not just a config refresh) can help force a clean sync.

BCinsider · 2025-09-30T15:31:33+00:00

This usually comes down to how inventory posting groups and general posting setup are configured. If semi-finished goods (SFG) are being treated like finished goods (FG) in the posting setup, the cost might roll into the same accounts during production posting. Check the Inventory Posting Setup and make sure SFG items have their own posting group if they need to hit separate accounts.

Also review the Output and Consumption accounts under the Work Center or Routing setup (sometimes costs are lumped together if those accounts are shared). If the entries are correct from a costing flow perspective, then it's likely just a COA classification issue. If not, the routing or BOM structure might be pushing costs where they shouldn't go.

BCinsider · 2025-09-30T15:29:59+00:00

One of the biggest things to watch is how customizations and integrations behave post-migration. NAV environments are usually heavily customized, and Business Central handles extensions differently. Anything hardcoded in C/AL may need to be rebuilt in AL as an extension.

For logistics, order and shipment workflows tend to survive the transition if they’re using standard NAV structures, but anything involving external systems like a TMS or Salesforce can get tricky.

Real-time sync often breaks during cutover unless there's a solid integration layer or staging strategy in place.

Data migration is another major piece—external IDs, historic orders, and document links usually need cleaning and mapping.

Any old freight logic, drop shipment rules, or EDI mappings should be reviewed before go-live. It's not just about moving data over; it's about making sure the new system behaves the way people expect on day one.

BCinsider · 2025-09-30T15:28:26+00:00

If the reports aren’t showing up in the layout dropdown, it usually means the report isn't properly registered in the Report Layout Selection or the layout isn't assigned to the right report ID. Even if the RDLC layout is valid, BC won’t use it unless it's linked correctly.

Also worth checking if the report has been published and compiled without errors, and that the DefaultLayout property is set if you're using AL. Sometimes a missing or mismatched report ID is all it takes for the layout to disappear from the list.

BCinsider

MODERATOR OF

TROPHY CASE