Understanding Your Requirements:

Before diving into the licensing options, it’s essential to assess your company’s specific needs and objectives. Consider factors such as the size of your organization, the functionalities required (CRM, ERP, or both), the number of users, and any specialized features your business demands. MindQuad Solutions Pvt Ltd, for instance, might prioritize CRM functionalities to optimize customer interactions and drive sales.

Exploring Licensing Options:

Microsoft offers a variety of licensing plans to accommodate diverse business requirements. For small to medium-sized enterprises (SMEs) like MindQuad Solutions Pvt Ltd, the Dynamics 365 Business Central license could be a suitable choice. This plan encompasses essential ERP functionalities such as financial management, supply chain optimization, and project tracking.

Alternatively, if your company focuses primarily on CRM operations, the Dynamics 365 Sales license might be more appropriate. This license equips your sales team with tools for lead management, opportunity tracking, and customer insights, empowering them to deliver exceptional service and drive revenue growth.

Customizing Your License:

One of the key advantages of Dynamics 365 is its flexibility in customization. Microsoft allows businesses to tailor their licenses by adding or removing specific modules and functionalities based on their unique requirements. MindQuad Solutions Pvt Ltd may opt to augment their Dynamics 365 Sales license with additional modules like Customer Service or Marketing to create a comprehensive CRM ecosystem.

Procuring the License:

Once you’ve determined the most suitable licensing plan, acquiring the license is a straightforward process. You can purchase Microsoft Dynamics 365 licenses directly from Microsoft’s official website or through authorized resellers like MindQuad Solutions Pvt Ltd. Ensure that you provide accurate information regarding your company size, user count, and desired functionalities to receive the appropriate licensing agreement.

Implementing Dynamics 365:

With your license secured, the next step is implementation. Microsoft offers extensive resources, including documentation, tutorials, and support services, to facilitate the deployment of Dynamics 365 within your organization. Collaborate with your IT team or engage the expertise of a certified Dynamics 365 partner like MindQuad Solutions Pvt Ltd to ensure a smooth and efficient implementation process.

The post Simplifying Your Business Dynamics: A Guide to Obtaining Microsoft Dynamics 365 License first appeared on Mindquad Solutions Pvt Ltd.

Almost all customers are doing business in multiple countries and regions across the world and due to this supply chain becomes more difficult to handle while maintaining cost and customer services. One huge advantage of using Microsoft Dynamics 365 is that it can support global business processes from a single cloud solution. Multiple currencies, time zones, languages, and compliance with multiple banking and reporting standards can all be managed from one solution, helping to provide consistency and standardization across various business entities around the world.

2. Flexible Pricing

Customers have to pay for what they need. Paying per user, per month means they get exactly what they ask for. Each application can be purchased individually, so they aren’t paying for utilities they don’t need.

3. Centralise Data

Customers get real-time reporting of their KPI’s with Power BI which helps in enhancing the sales performance with data visualizations. Provide them to manage the organization in a better way by data-driven decision-making tools.

4. Deep Integration

Integration with other applications such as Outlook, Excel and Word. These synchronization capabilities bring unmatched benefits. 

5. Automate Processes and User Control

No need to perform the repetitive manual tasks and provide Approval Workflow which keeps control over users and streamlines the processes.

6. Excellent User Interface

Spending less time and money to onboard employees of the organization as they easily adapt to this new platform.

Source – https://www.serversys.com/10-reasons-to-choose-dynamics-365/   https://sunrise.co/blog/5-great-reasons-brands-choose-microsoft-dynamics-365/

The post Top Reasons why customers choose Microsoft Dynamics 365 ERP System first appeared on Mindquad Solutions Pvt Ltd.

Table Extension Object helps to create more fields and allows to change some of the properties in an Existing table. By this object, we can store more data in the same table and customize the tables.

Before using this object, we must note that,

1. We can use this object to extend Table only if “Extensible Property” set to ‘TRUE’ in that Table.
2. System Tables and Virtual Tables cannot be Extended.
3. Object’s name length should not be more than 30 characters.

Uses:

1. Adding More Fields: We can add more fields in a particular Existing Table and write trigger code for new fields. We can use the ‘OnLookUp’ and ‘OnValidate’ fields to trigger the same as we use in Table.
2. Writing new Trigger codes: We can use the same triggers for Table Extensions as we use for Tables. For example, if we need to throw an error before the modification takes place in the existing tables then we can add ‘OnBeforeModify’ Trigger in The Table Extension Object.
3. Adding Keys: Just like in the table object, we can define new keys. We can also add keys for new fields added by the Table Extension, if we need to extend keys provided in the existing Table.
4. Change of properties: Since Table Object and Table Extensions Object properties are almost the same, so we can add some table properties as we want to customize them.

Table Extension Object Syntax:

tableextension Id MyExtension extends MyTargetTable

{

  fields

  {

    // Add changes to table fields here

  }

  var

    myInt: Integer;

}

The post Table Extension Object first appeared on Mindquad Solutions Pvt Ltd.

Salvage value is also known as Scrape Value.

Salvage value or Scrap Value is the estimated value of an asset after its useful life is over and therefore, cannot be used for its original purpose.

The value of machinery (any manufacturing machine, engineering machine, vehicles etc.) after its effective life of usage is known as Salvage value. In other words, when depreciation during the effective life of the machine is deducted from the Cost of machinery, we get the Salvage value.

Salvage value In Business Central

In Business Central, whenever we require any information related to Fixed Asset, we can directly go into the Fixed Asset Card. Where we can get all the information like – Book Value of Asset, Depreciation % and also the Salvage value for the Asset.

In the above image, in salvage Value field is showing blank.

In Business Central, we have to post salvage value through Fixed Asset Journal.

 The formula for Salvage Value –

S = P – (I * Y)

Where,

• S = Salvage Value
• P = Original Price
• I = Yearly Depreciation Amount
• Y = Number of Years

SALVAGE VALUE FORMULA

• Engineering machinery costing INR 100,000 has a useful life of 7 years. The amount of depreciation is INR 10,000 / year. Calculate the Salvage value of the machinery after 7 years.

Salvage value is calculated given the Formula below

S = P – (I * Y)

• Salvage Value =INR 100,000 – (INR 10,000 * 7)
• Salvage Value =INR 100,000 – 70,000
• Salvage Value = INR 30,000

Therefore, the salvage value of the machinery after its effective life of usage is INR 30,000.

HOW WE CAN POST SALVAGE VALUE IN BUSINESS CENTRAL

After calculating the formula manually, now in the Business central, we can post the salvage value amount for the Fixed Asset through Fixed Asset Journal-

Our salvage value calculated amount is 30000 Rupees.

From Fixed Asset Journals, we can post the Salvage value amount for the Fixed Asset.

Earlier on the Fixed Asset Card page, the salvage value is showing blank.

After posting the salvage value for the Fixed Asset, the Salvage value of the fixed Asset is showing 30000 Rupees.

The post SALVAGE VALUE IN DYNAMICS 365 BUSINESS CENTRAL first appeared on Mindquad Solutions Pvt Ltd.

Now:- New Item Categories feature provides multi-level hierarchy functionality and thereby does the same and more than the Product Group feature.

Now Microsoft has introduced a Subcategory in the Item Category. i.e., in Item Category, there is Parent Category we can add Item Category. For the parent category, the Highlighted field will be empty and for subcategories, we can select the parent category.

On the List Page, the Parent category is highlighted in bold.

Item Category Card Page:-

Attributes also we can add as per Item Category.

Attributes for parent category are flowed to subcategory and in the sub category, we can add new attributes if we want.

The post Product Group Code Feature Replaced by Item Categories Feature first appeared on Mindquad Solutions Pvt Ltd.

source code as below

OBJECT Page 50240 License Check

{

  OBJECT-PROPERTIES

  {

    Date=02-09-16;

    Time=18:17:33;

    Modified=Yes;

    Version List=V.01;

  }

  PROPERTIES

  {

    SourceTable=Table2000000043;

    SourceTableView=SORTING(Object Type,Object Number)

                    ORDER(Ascending)

                    WHERE(Object Type=FILTER(Table|Query|XMLport|Page|Report|Codeunit));

    PageType=List;

    OnAfterGetRecord=VAR

                       LiceanceCheck@1000000000 : Record 2000000043;

                     BEGIN

                       CLEAR(Name_Txt);

                       CLEAR(Var_Tx);

                       IF “Object Type” = “Object Type”::Table THEN

                       BEGIN

                         IF Object_Lrec.GET(Object_Lrec.Type::Table,”,”Object Number”)THEN

                         BEGIN

                            Name_Txt := Object_Lrec.Name;

                            Var_Tx := Object_Lrec.”Version List”;

                         END;

                       END ELSE IF “Object Type” = “Object Type” ::Codeunit THEN

                       BEGIN

                         IF Object_Lrec.GET(Object_Lrec.Type::Codeunit,”,”Object Number”)THEN

                         BEGIN

                            Name_Txt := Object_Lrec.Name;

                            Var_Tx := Object_Lrec.”Version List”;

                         END;

                       END ELSE IF “Object Type” = “Object Type”::Page THEN

                       BEGIN

                         IF Object_Lrec.GET(Object_Lrec.Type::Page,”,”Object Number”)THEN

                         BEGIN

                            Name_Txt := Object_Lrec.Name;

                            Var_Tx := Object_Lrec.”Version List”;

                         END;

                       END ELSE IF “Object Type” = “Object Type”::Report THEN

                       BEGIN

                         IF Object_Lrec.GET(Object_Lrec.Type::Report,”,”Object Number”)THEN

                         BEGIN

                            Name_Txt := Object_Lrec.Name;

                            Var_Tx := Object_Lrec.”Version List”;

                         END;

                       END ELSE IF “Object Type” = “Object Type”::Query THEN

                       BEGIN

                         IF Object_Lrec.GET(Object_Lrec.Type::Query,”,”Object Number”)THEN

                         BEGIN

                            Name_Txt := Object_Lrec.Name;

                            Var_Tx := Object_Lrec.”Version List”;

                         END;

                       END ELSE IF “Object Type” = “Object Type”::XMLport THEN

                       BEGIN

                          IF Object_Lrec.GET(Object_Lrec.Type::XMLport,”,”Object Number”)THEN

                          BEGIN

                             Name_Txt := Object_Lrec.Name;

                             Var_Tx := Object_Lrec.”Version List”;

                          END;

                       END ELSE;

                     END;

  }

  CONTROLS

  {

    { 1000000000;0;Container;

                ContainerType=ContentArea }

    { 1000000001;1;Group  ;

                Name=Group;

                Editable=FALSE;

                GroupType=Repeater }

    { 1000000002;2;Field  ;

                SourceExpr=”Object Type” }

    { 1000000007;2;Field  ;

                SourceExpr=”Object Number” }

    { 1000000010;2;Field  ;

                Name=&Name;

                SourceExpr=Name_Txt }

    { 1000000011;2;Field  ;

                Name=&Version List;

                SourceExpr=Var_Tx }

    { 1000000003;2;Field  ;

                SourceExpr=”Modify Permission” }

    { 1000000004;2;Field  ;

                SourceExpr=”Delete Permission” }

    { 1000000005;2;Field  ;

                SourceExpr=”Execute Permission” }

    { 1000000006;2;Field  ;

                SourceExpr=”Limited Usage Permission” }

    { 1000000008;2;Field  ;

                SourceExpr=”Read Permission” }

    { 1000000009;2;Field  ;

                SourceExpr=”Insert Permission” }

  }

  CODE

  {

    VAR

      Name_Txt@1000000000 : Text;

      Var_Tx@1000000001 : Text;

      Object_Lrec@1000000002 : Record 2000000001;

    BEGIN

    {

      MQSHAPAR-02Sep16

    }

    END.

  }

}

The post License Information first appeared on Mindquad Solutions Pvt Ltd.

Item Setup: To set up items that are currently available in stock, specify their unit of measure, costing method, inventory posting group, unit cost and price and other properties. There are three types of items as follows:

1. Inventory: Items that are needed for day-to-day production/selling and has high value.
2. Non-Inventory: Low-cost physical Items for internal use that are not a part of regular inventory but are ordered as per requirement.
3. Service: Non-physical Items which represents services/Labour time.

Warehouse Setup: Each user performing warehouse related activities must be set up as a warehouse employee assigned to a particular location.

Bins: Items can be assigned to bins for better management of inventory. In location master, if you have checked the Boolean – “Bin mandatory”, then you need to specify bin whenever you try to move the stock within the warehouse.

Item Tracking: Serial No. and Lot No. are tracked by Item Tracking. You can manage stock using serial numbers or Lot numbers. Assigning these numbers can be manual or automatic as per the requirement of the user.

Stock Transfer: Stock can be moved from one location to another by creating transfer orders. Using this, you ship the outbound transfer from one location and receive inbound transfer at the other location. You can also use an item reclassification journal to transfer stocks.

Picks and Put Aways: Create pick and put-away orders. If you want to make Pick/Put-Away mandatory, then you need to tick the check box “Require Pick”,” Require Put-Away” available in Location Master.

Warehouse Receipt: In the purchase order, you can find the action named Created Warehouse Receipt. By clicking this, the warehouse will be expecting the goods as on the delivery date. Once received, the goods are moved to their assigned bin in a storage location.

Gate Entry: Gate Entry is the record of goods entering/leaving the premises. This also helps in tracking the vehicle details, time in and time out, the person accompanying the vehicle etc.

Physical Inventory Counting: This process is done periodically to verify whether the total physical count of the inventory matches the NAV inventory count. If the values are mismatched, then the difference is posted via positive/negative adjustment in the physical inventory journal. Item transactions, such as sales, purchase, negative and positive adjustments can be posted from item journals.

THE FOLLOWING IMAGE EXPLAINS THE WAREHOUSE FLOWS

The post INVENTORY MANAGEMENT first appeared on Mindquad Solutions Pvt Ltd.

This article is showing how easy it is to use two slicers to compare any two items. I specifically showed how you could compare any 2 years of choice. The way to limit the choices in the comparison slicer to exclude the item selected in the first slicer.

Example: –

If I select Year = 2019-20 in slicer 1 below, then I don’t want to see Year = 2019-20 in the comparison slicer 2 below. 

• “From Financial Year” Slicer comes from one table & “To Financial Year” Slicer comes from another table. Table visual showing comparison between selected year value.

Selected value from one slicer is automatically remove from second slicer. This is very useful when we need to comparison dynamically. Let’s see how this task is achieved.

• Go to Table tools tab -> select new table & Create Table “Compare From” from Financials.

• Go to Table tools tab -> select new table & Create Table “Compare To” from Financials.

• Now Create one measure.

FY Selection Control =

IF (

SELECTEDVALUE (‘Compare From'[From Financial Year]) = SELECTEDVALUE(‘Compare To'[To Financial Year]),0,1
)

• Now set measure value in filter pane of both slicers.

Set Value 1 for both slicer in Filter Pane

CONCLUSION: –
With the help of this method, we can achieve our goal. So, you can use this method to achieve different goals in your report and make measure as per your requirement.

The post Dynamically Change Value One Slicer Based on Another Slicer first appeared on Mindquad Solutions Pvt Ltd.

Data model Developing with Power BI is effortless and rapid. User do not need to roll out data into several table. Once you’ve dragged in data from numerous resources, one can form a model by merely linking tables applying relationships. Though, terrific flexibility comes from great accountability. It is very questionable that the resource data is already extremely well-defined for the sort of analysis the user would like to perform. If the users only link up source tables with relationships, devoid of following data modelling standards, too frequently this will cause in complicated models of data that are high-priced to keep. If the number calculating does not match up, or if the DAX procedures are very complicated to retain, users will most likely have got an issue in a data model. A data model is like the groundwork for your home, make it right and the consequent construction, and the home itself, will be of good quality.

Data modelling is a fundamental expertise that anyone thought-provoking in developing BI reports should understand. Being a great data modeller means being capable to match up your particular model with one of the various distinct configurations that have previously been learned and resolved. A wonderful presentation to this matter is the book: Analyzing Data with Power BI and Power Pivot for Excel, written by M. Russo and A. Ferrari. Nevertheless, to turn out to be a excellent data modeler user will need knowledge, which means you may perhaps have to endure several breakdowns as you find out.

The main key data modelling decision is granularity, i.e. the intensity of detail in tables. User must have the proper degree of granularity to meet up reporting demands. If granularity is extremely rough user will not be skilled to obtain the data, user would like. Furthermore, very well granularity involves bigger and unhurried datasets, and theoretically intricate DAX formulas. For example, if your Sales table includes data for the specific operations but you only require reporting by month, quarter and year, the precise level (or granularity) would be a calendar month.

A further significant data modelling decision is the degree of normalisation. The most frequent reporting data sources are operational systems, such as Dynamics NAV. An operational system immediately supports the implementation of a business procedure by acquiring details regarding significant business outcomes or operations. Hence, operational databases are extremely normalised and enhanced for insertion and update operations. Though the focus of the operational system is the implementation of a business procedure, the BI system, such as Power BI, supports the evaluation of the procedure. Interface with a BI system takes place completely through and through queries that just recall data about business procedures. When users only read out data, normalisation is infrequently a good practice. The performance of the database is improved when there are a small number of joints involved.

Dimensional modelling has been announced as an immediate retort to the exclusive needs of BI systems. A star schema is the humblest structure of a dimensional model, in which data is categorized into statistics and dimensions.

Conclusion

Automatic analytics gizmo plays a crucial title role in business and helps out to examine gigantic data. Power BI is a business intelligence and analytical tool to competently scrutinise and envisage massive volumes of data. From this blog, we have discovered a bit of data modelling, its usage, and how it can effectively make the preferred end result in Power BI. But with the help of Power BI and DAX Expression, we evaluated our preferred data and pictured it in a superior way. Power BI is inexpensive business analytics means when used efficiently.

The post Modelling of Data in POWER BI first appeared on Mindquad Solutions Pvt Ltd.

Standard Cost Account: 

In Standard Costing, we assign The Specific Standard Cost OF Direct Material, Direct Labor & Overhead Expenses to Product Other Wise Then Actual Cost of Material, Labor & Overhead. These Standard Costs Are Based on The Standard sufficient Cost of Material, Labor & Overhead As per Standard follow By Industries.

Although The Standard Cost Assigned to the Product or Service, The Business Will Still Have to Pay the Actual Cost of Direct Material & Labor. So, They Will need to Calculate the Difference Between Standard Cost & Actual Cost for Finding Out Whether They Have Spending More OR Not As per the Planned Amount. This Analysis Known as Variance Analysis.

By the Variance Analysis, If We Found That the Actual Cost Is Higher Than the Expected Cost It Will Be Make Adverse Effect on Business Profit and Company’s Profit Will be Lesser than the Anticipated Profit. If the Actual Cost Is Lesser Than the Expected Cost, it Will Make Favorable Effect on Business Profit and Company’s Profit Will be More than the Anticipated Profit.

For Example

Example 1 

As Per Standard Industries Practice for Production Of 1 Unit of FG Product We Required 2 Kg Of R/M @ 200 Per Kg & Direct Labor 1.5 Hrs. @ Rs. 50 per Hrs.

But Actual Company Spend Following for Production Of 1000 Unit Of FG.

Material = 2000 Kg @ 210

Labor Cost = 1500 Hrs. @ 55 Per Hrs.

Example 2

As Per Standard Industries Practice for Production Of 1 Unit of FG Product We Required 2 Kg Of R/M @ 200 Per Kg & Direct Labor 1.5 Hrs. @ Rs. 50 per Hrs.

But Actual Company Spend Following for Production Of 1000 Unit Of FG.

Material = 1800 Kg @ 210

Labor Cost = 1400 Hrs. @ 55 Per Hrs.

As Per Above Example We Can See That Even Though Worker Should Work More Efficiently But Due To Increase In Price Of Labor & Material It Seen Less Favorable AS It Have.

The post Cost Accounting in Dynamics 365 Business Central first appeared on Mindquad Solutions Pvt Ltd.