total network inventory demo  - Activators Patch

Assign licenses to devices or deployments; View inventory and assignments of current licenses. Available License Types. Perpetual License (never expires). Trial. Network Inventory Advisor – Network Management, Hardware and Software Inventory Audit, License Audit. Free Trial. With complete visibility and granular control over your entire software inventory. Get a Demo White Arrow image · Product Sheet.

Thematic video

Total Network Inventory: hardware inventory, PC audit software, computer inventory.

Total network inventory demo - Activators Patch -

Meraki Co-Termination Licensing Overview

  1. Last updated
  2. Save as PDF

All current Cisco Meraki products require valid licensing to operate. This article describes how Cisco Meraki Co-Termination licensing operates and applies to an organization. All licensing-related operations can be performed from the Organization > Configure > License Info page.

For more information about the License Info page specifically, please refer to our License Info Page article. 

Co-Termination

The Cisco Meraki Co-Termination licensing model works on the basis of co-termination, which means that for any given organization, regardless of how many licenses were applied or when they were applied, the license expiration date for all licenses claimed to that organization will be exactly the same. This is accomplished by averaging all active licenses together and dividing by the license limit count of devices in the organization.

image.png

For example, suppose an organization had two separate Enterprise AP licenses, one license for 2x APs spanning one year (365 days) and another for 1x AP spanning five years (1,825 days). The co-termination value would be calculated as ((1825*1)+(365*2))/3= 851 days total for all three APs. So assuming all three licenses were applied on the same day, the organization would have a co-term date of 851 days from the start date of the licenses.

If the licenses were not applied at the same time, for example if the five-year license was applied halfway through the one-year license, the co-term calculation will take that into effect. In this case, the calculation would be ((1825*1)+(182*2))/3=730 days total for all three APs.

Note: The organization co-terminationdate does not depend on the current device count, but rather the license limit. Removing devices from a network or organization will not impact the co-termination date.

 

To calculate how licenses impact each other in an organization, check out the License Calculator. To see a more detailed explanation and the exact calculations that are used to determine co-term dates, please refer to our detailed co-term explanation page.

License Start Date

Licenses in the Co-Termination model start consuming time from the date purchased, not the date they are added to an organization.

Note: Waiting to activate a license in the dashboard does not delay its activation date. There is no time benefit gained from delaying an activation.

Device types

Licenses are sold based on the specific model of device, so for example, an MS220-24 will require a separate license from an MS220-8. This applies even to PoE vs. non-PoE versions of devices and wireless vs. non-wireless versions for MX devices. For example, an MS220-8 will require a different license than an MS220-8P, and an MX64 license will not work for an MX64W.

Organization-Wide Licensing

Cisco Meraki licensing is applied on an organization-wide basis. This means that a license isn't purchased for a specific serial number or device, rather each license added to the organization increases the number of a specific device type (the license limit) that can be added to networks within the organization.

The 30-Day Grace Period 

The number of devices in an organization can not exceed the license limits. If this occurs, the organization will enter a 30-day grace period, during which the organization must be brought back into compliance, otherwise it will be shut downuntil proper licensing is applied to the organization. 

Note: During the grace period, network clients will not see a difference.

Should an organization enter the 30-day grace periodbecause of exceeding device license limits,it can be brought back into compliance either by removing devices from networks within the organization or through purchasing additional licensing. The only other time an organization will enter this 30-day grace periodwould be if its licensing has expired by passing the co-termdate. If this occurs, the only way to bring it back into licensing compliance is through the purchase of additional licensing.
 
For example, if an AP is added to an organization that already has five APs and licensing for ten APs, no additional licensing is required because the organization's license limitis higher than the number of APs in the organization. But if an MX series security appliance was added to the same organization, it would enter the 30-day grace periodbecause the organization is not licensed for MX security appliances. For more information about the 30-day grace period, read the License Limit and Current Device Count section of this article or refer to the License Info article.

License Limit and Current Device Count

The image below shows an example License Limit and Current Device Count table for an Organization. Notice how each hardware model has it's own individual License Limit and Current Device Count. Each column is explained in more detail below.

DeviceCount.png

License Limit

The License Limit is defined by the sum of the device count for all currently active licenses applied to an Organization. Licenses that have been Invalidated or were applied prior to the most recent Renewal operation will not be counted when calculating the License Limit. For example, if an Organization has three active licenses, one license for 1x MX65, one license for 2x MR devices, and one license for 1x MS220-8P and 1x MR device, the total License Limit for that Organization would be 1x MX65, 1x MS220-8P, and 3x MR devices. 

Current Device Count

The Current Device Count column lists the total number of each type of device that is currently added to any network inside the Organization. Devices that are claimed to the Organization Inventory but not added to any Networks will not count towards the Current Device Count. For example, if one network has 1x MX65 and 2x MR33, and a second network has 1x MS220-8P and 1x MR52, the Current Device Count for that Organization would be 1x MX65, 1x MS220-8P, and 3x APs.

Note: All MR and MV series devices are grouped under the same respective licensing group. So an MR18 will require the same license as an MR72 and both will count equally toward the total device count of MR devices.

 

The Current Device Count does not impact the Co-Term date of an Organization, the Co-term date is instead calculated based on the License Limit of the Organization. Because of this, adding or removing devices from networks will not affect the Co-term date of the Organization except in situations where adding a device will put the Organization outside of its License Limit and invoke the 30 day Grace Period. In this situation, either removing the device(s) from the Network(s) or adding the required licensing prior to the end of the 30 day Grace Period will put the Organization back into compliance. If new licensing is added, the Co-term date will be updated to reflect this change. If no new licensing is added then the Co-term date should remain unchanged. 

 

Licensing Options

MR Licensing Options

The MR access points only have one license type, a general "wireless AP" license. This license can apply to any Meraki access point, so long as there is one license for every AP in the account. For example, a network containing 2x MR18s and 1x MR32 will require licensing for 3x APs.

MS Licensing Options

Classic MS switches have licenses on a per-model basis, so every MS model has a corresponding license. Please note that these licenses are non-transferrable between switch models. For example, an MS220-48 switch will not be covered by an MS320-48 license; it will require an MS220-48 license.

MS390 Licensing Options

MS390 license structure includes two feature tiers:  Enterprise and Advanced. The MS390 also introduces a new and simpler license to hardware mapping, specifically 24-port or 48-port licenses. As with all MS, every MS390 license is available in 1, 3, 5, 7, and 10 year terms.

 

MS390 License Structure24-Port Model48-port Model
Advanced FeaturesLIC-MS390-24ALIC-MS390-48A
Enterprise FeaturesLIC-MS390-24ELIC-MS390-48E

The features available with advanced licensing are: 

  • Adaptive policy *
  • Greater than 1,000 routes for OSPF

* Available in a future software release

In the Co-term licensing model (most existing Organizations), an Organization must either have all MS390 Enterprise or all MS390 Advanced licenses - they cannot be mixed. In the Per-device licensing model, a mix of Enterprise and Advanced can be added to a single Organization, but certain features may require all devices in a Network to have Advanced licenses, e.g. Adaptive Policy.

For more information on licensing, refer to Meraki Licensing Models article.

MX Licensing Options

The MX security appliances have licenses on a per-model basis, so every MX model has a corresponding license. Please note that these licenses are non-transferrable between appliance models. For example, an MX64 will not be covered by an MX84 license; it will require an MX64 license.

The MX security appliance has multiple license editions: Enterprise, Advanced Security, and Secure SD-WAN Plus. Please note that the MX licensing edition is uniform across the organization. For example, you can have all 25 appliances using Enterprise Edition or Advanced Security Edition or Secure SD-WAN Plus Edition, but you cannot have 20 appliances using one edition and five using the other edition. If you wish to use Enterprise Edition for some appliances and Advanced Security Edition for other appliances, you need to create two organizations, one for your appliances with the Enterprise Edition, and another for the appliances with the Advanced Security Edition. Similar concept appliance for Secure SD-WAN Plus Edition as well.

 

For additional information and feature details, please refer to the MX Security and SD-WAN Licensing article.

SM Licensing Options

Meraki Systems Manager has only one license type, which is used for all managed clients in SM regardless of operating system type. Licenses need to be available for devices to enroll into your network. 

Please refer to our documentation for more information on Systems Manager Licensing.

Managing Licenses

Adding New Licenses

From the Organization > Configure > License Info page, the Add another license link allows organization administrators to add additional licensing to their organization. This can be done to either increase the total number of devices licensed to the organization or to renew the existing licensing for all devices in the organization. Adding additional licensing to an organization is a simple five-step process, outlined below.

  1. Click Add another license.
  2. Choose either License more devices or Renew my Dashboard license.
  3. Enter the 12-digit license key you would like to claim.
  4. Click Add license.
  5. Review the changes on the License Info Preview Page.
  6. Fill in the box next to Enter the new license expiration to confirm this addition with the expiration date seen above (otherwise the Add license button will be greyed out).
  7. Click Add license again to finish claiming the license.

 

clipboard_e3f138159f39ba196eb43489cc23e6925.png

Note: Claiming a new license with the claim type of License more devices will simply add the new license count to the existing license limit of the organization and alter the co-term date appropriately.

Warning: Claiming a new license with the claim type of Renew my Dashboard license will invalidate any previouslicense limit counts and force the organization license limit to match only licenses applied during or after the most recent renewal action, in addition to altering the co-term date for the organization. 

Renewing Your Dashboard Licensing

When a license key is applied using the Renew my Dashboard license operation, the organization’s licensing state updates to exactly match the device count of that license key, and any remaining time from previous licenses is kept and added to the new co-term date. For example, if an organization with licensing for 5x APs were to have a 2x AP, three-year license applied as a renewal, that organization would only be licensed for 2x APs for three years, plus the remaining time from prior to the renewal. In this instance, the organization would be 3x APs over the license limit, and therefore out of compliance.

Note: The recommended practice for applying a renewal is to purchase a single license key that covers all devices currently in the organization for X number of years. Applying that license key as a renewal will then extend the organization’s co-termdate by that many years while keeping the same license limitfor devices.

 

Even if the organization is in compliance, (co-term date has not passed and the organization has not yet expired or been shut down,) the renewal license should still be applied immediately because the time on the license starts counting down from the date purchased.

Warning: Holding onto a license does not delay its activation date. There is no time benefit gained from delaying a renewal.

Moving Licenses

A co-term license can be requested to be moved between organizations. Only organization administrators have permission to request licenses moves and are required to have access to both organizations. 

Moving co-term licenses can only be done by Meraki Support. Please call or open a case to move licenses.

NOTE: Co-term licenses cannot be moved to per-device licensing (PDL) organizations.

License Conversion

The following list reflects all supported license model conversions by Meraki Support in a co-term org. These license conversions are not supported in a per-device licensing org. If you have received a different model device as the result of a device-RMA, we can update the license to reflect that change. Licenses can also be converted if the request is a valid conversion from the list below and the license key is outside the 30-day license-RMA window. 

These are the supported conversions:

  • MX60/W → MX64/W (MX65 conversions NOT allowed)

  • MX64/W → MX60/W

  • MX65W/64W/60W → MX65/64/60

  • MX65/64/60 → MX65W/64W/60W (MX65 to MX65W, MX64 to MX64W and MX60 to MX60W are only allowed)

  • MX64/W → MX67/W

  • MX65/W → MX68/W

  • MX80 → MX84

  • MX84 → MX80

  • MX84 → MX85

  • MX90 → MX100

  • MX100 → MX95

  • Z1 → Z3

  • vMX-100 → vMX-M

NOTE: Keys that fall within the 30-day RMA window MUST be RMAd and repurchased. There is no exception to this. 

License RMAs can be submitted at meraki.com/rma in an incognito/private browser window.

Removing and Undoing License Claims

There are a number of licensing issues that are caused by misapplication of a single license key. If a license has been applied incorrectly, the undo license claim tool can be used to remove the license so it can be re-added correctly.

This article will explain how to remove licenses from organizations, using the undo license claim tool.

Use Cases

There are two common situations where a license application can cause problems on an organization:

  • License was applied to the wrong organization.
    A license may have accidentally been applied to the incorrect organization. The undo license claim tool will release the license so it can be applied to the correct organization.
  • License was incorrectly applied as a renewal or add devices.
    When a license key is applied to an organization, there are two options for the license type: Renewal or add devices. Applying a license as the incorrect type will have an undesired effect on the organization's licensing, and will likely take the organization out of compliance. The undo license claim tool can be used to remove the license, so it can be reapplied correctly.
    For more information on different ways to apply licenses, please refer to our documentation regarding Licensing Guidelines and Limitations.

Using the Undo License Tool

The undo license claim button will only be available within 7 days of the license application. For issues with older licenses, please follow these steps:

  1. Make sure you are a full organization administrator on both organizations. If not, this process will need to be followed by another admin.
  2. Contact Meraki Support via phone or email licensing@meraki.com with the following information:
    • Your support passcodes for both the source and destination organizations.
    • The URL for both organizations License Info pages.
    • The license key to be transferred and the device models and the number of devices that need to be moved to the new organization.

 

The following steps explain how to undo a license application:

  1. In Dashboard, navigate to Organization > Configure > License info.
  2. Click the undo button next to the license in question:
  3. Review the confirmation window that pops up. If you are sure this is the correct license to remove, click Yes:

 

Upon confirming the change and closing the pop-up, the organization will be reverted to the previous licensing state. The original license will be invalidated, so a replacement key will be generated. The new license key can then be re-applied or added to another organization for the remaining license term. The new license key can also be found under Organization > Change log.

Out-of-Licensing Compliance Warnings and Solutions

Cisco Meraki devices use the Cisco Meraki cloud for centralized management and control. The Cisco Meraki cloud is licensed on a “per device, per year” basis. Each organization is licensed for a certain number of devices through a termination date. When out of compliance, due to expiration of licenses or insufficient device counts, you will be notified by e-mail.

This e-mail will begin with "Thank you for being a valued Cisco Meraki customer. Our records show that your organization is over the device limit for your Cisco Meraki Cloud license."

To see the current status of your licensing, login to Dashboard and go to Organization > License info. This page will include information about your licensing status, MX Advanced Security features (if applicable), license expiration date, and details of your current and licensed device counts. Points where you are out of compliance will be indicated in red. To return your organization to a compliant status, you will need to purchase the appropriate licensing. 

For more information about Cisco Meraki licensing, please review the Licensing FAQ.

To purchase licensing, contact your Cisco Meraki account executive, or visit Sales Contacts.

Out of Compliance Examples

Over Device Limit

In this case, the organization has one additional MS220-8P device in a network than they are licensed for, and would need to purchase the necessary license in order to achieve compliance. 


clipboard_e52220f1919c08ff800c119d81cd08717.png

Since devices that are not in a network do not count towards the device count, the MS220-8P can be removed from its network and left in the organization inventory until additional licensing is added.

Licensing Expired

In this case, licensing for the organization expired on May 11th. The licenses would need to be renewed, or new licenses purchased in order to return to a compliant state. 

Licensing Expired & Network Shutdown

In this case, licensing for the organization expired and the organization has been shutdown. This will not occur until after the 30 day grace period, and may also occur if the organization has been in excess of the licensed device count.

Compliant Licensing

In this case, the organization has more device licenses than they have devices and their licensing will expire in 899 days.

Источник: https://documentation.meraki.com/General_Administration/Licensing/Meraki_Co-Termination_Licensing_Overview

The Intel vPro® Platform: Built for Business

Product and Performance Information

1

Intel does not control or audit third-party data. You should consult other sources to evaluate accuracy.

2

Results have been estimated or simulated.

4

As measured by Microsoft Office 365 workflow 11th Gen Intel® Core™ vPro® i7-1185G7 Processor vs. 8th Gen Intel® Core™ vPro® i7-8650U Processor.

5

In thin and light Windows-based PCs.

6

As measured by PC Mark 10 Application overall score 11th Gen Intel® Core™ vPro® i7-1185G7 Processor vs. 8th Gen Intel® Core™ vPro® i7-8650U Processor.

7

As measured by Productivity and Collaboration Workflow 11th Gen Intel® Core™ vPro® i7-1185G7 Processor vs. 8th Gen Intel® Core™ vPro® i7-8650U Processor.

8

As measured by Video Editing workflow. 11th Gen Intel® Core™ vPro® i7-1185G7 Processor vs. 8th Gen Intel® Core™ vPro® i7-8650U Processor.

9

As measured by Productivity and Collaboration Workflow. 11th Gen Intel® Core™ vPro® i7-1185G7 Processor vs. AMD Ryzen 7 PRO 4750U.

10

As measured by Microsoft Office 365 workflow. 11th Gen Intel® Core™ vPro® i7-1185G7 Processor vs. AMD Ryzen 7 PRO 4750U.

11

As measured by SYSmark 25 overall score. 11th Gen Intel® Core™ vPro® i5-11500 and AMD Ryzen 7 PRO 4750G.

12

As measured by Microsoft Office 365 workflow. 11th Gen Intel® Core™ vPro® i5-11500 and AMD Ryzen 7 PRO 4750G.

13

Intel Control-flow Enforcement Technology (CET) is designed to help protect against jump/call-oriented programming (JOP/COP) attack methods and return-oriented programming (ROP) attack methods, malware known as memory safety issues and which comprise over half of ZDI-disclosed vulnerabilities. Visit www.intel.com/11thgenvpro for details. Results may vary.

14

In thin & light Windows-based PCs, based on December 2020 IOActive study (commissioned by Intel) comparing malware detection by Intel 11th Gen Core vPro® platform with Intel® TDT and AMD Ryzen Pro 4750U-based system. Visit www.intel.com/11thgenvpro for details on Intel's industry-leading CPU behavior monitoring technology. Results may vary.

15

“The Total Economic Impact™ of the Intel vPro Platform,” an Intel-commissioned study by Forrester Consulting, January 2021, which surveyed 416 ITDMs at enterprises across the world using Intel vPro® platforms, including US, UK, Germany, Japan, and China. 91% respondents marked “agree” or “strongly agree” to this statement. Read the full study. Results may vary.

16

“The Total Economic Impact™ of the Intel vPro Platform,” an Intel-commissioned study by Forrester Consulting, January 2021, which surveyed 416 ITDMs at enterprises across the world using Intel vPro® platforms, including US, UK, Germany, Japan, and China. 90% respondents marked “agree” or “strongly agree” to this statement. Read the full study. Results may vary. For the purposes of this data, there are two assumptions being made to simplify analysis and explanation: 1) The composite organization assumes 100% laptop use — this helps simplify having to break out secondary inputs of device type counts and costs, which readers can do for their own business case analyses; 2) The composite organization assumes no growth to avoid attributing organic growth with value gains attributable to vPro, or complex explanation to subtract those gains from the ROI that is specific to the Intel vPro platform investment. Results may vary.

17

“The Total Economic Impact™ of the Intel vPro Platform,” an Intel-commissioned study by Forrester Consulting, January 2021, which surveyed 416 ITDMs at enterprises across the world using Intel vPro® platforms, including US, UK, Germany, Japan, and China. 74% respondents marked “agree” or “strongly agree” to this statement. Read the full study. Results may vary.

18

“The Total Economic Impact™ of the Intel vPro Platform,” an Intel-commissioned study by Forrester Consulting, January 2021, which surveyed 416 ITDMs at enterprises across the world using Intel vPro® platforms, including US, UK, Germany, Japan, and China. 84% respondents marked “agree” or “strongly agree” to this statement. Read the full study. Results may vary.

Источник: https://www.intel.com/content/www/us/en/architecture-and-technology/vpro/vpro-platform-general.html

General benefits

Microsoft have released a new exam for the Commerce functional consultant.  I did take this exam in the beginning of July, and it can take a few weeks before the results come.  But I’m pretty sure I will fail.  The exam was quite hard and there was just too little time. I got 62 questions, but only managed to answer approx. 45 of them within the timeframe of 90 minutes.  If you think MB-300 was difficult, then MB-340 is harder!

This blogpost is therefore my study notebook to retake the exam(if I fail😊).  You will not find any of the exam questions or answers here, but if you follow this steps, I think you will be closer to achieving your goal of passing the MB-340 exam, and also to understand the topic better.  The chapter and headlines are organized accoring to the skills measured list of MB-340.

Disclaimer:  Some texts and pictures are copied from the Microsoft learn, docs. demo environments and other sites.  In most cases you should find a hyperlink to the original source for a deeper study, and there are no guaranties that all here is right.  You should always refer to the official Microsoft documentation and training.

Enjoy and god luck studying.

Configure prerequisites and commerce parameters

Create employee and customer address books

Employee and customer address books are used to limit the personal to specific stores/POS or what information the employee should be see in HQ.  How to create an address book is documented here. One nice feature here is that the address book is the basis for the extensible data security (XDS) policy, that limits what stores and transactions a HQ user can access.  To make the XDS to work, remember to assign the correct Retail* roles to the users.  This will ensure that the address book filtering is working as expected.

What I normally recommend is to have one address book per store, one for the region, one global address book and one address book for customers.  If there are multiple brands, I also have customer address book for this.  Keep in mind that you can select multiple address books towards stores, employees, and customers.  I also like to think of address books as a hierarchy, and this allows for ensuring that regional managers can see their information and transactions across stores, while a store clerk only see information relevant to his job.     

Configure and manage retail workers

Retail workers are setup using features from the HR features, but the workers table is accessible from the retail menu.  Commerce lets you perform the following employee management functions:

  • Create entities for jobs, positions, and workers
  • Assign workers to more than one store
  • Configure different language settings for each user and user-based POS screen layouts
  • Limit the list of allowed operations

Additionally, you can configure the POS permission groups to associate different employees with different roles. The task management feature offers productivity enhancements for employees at the stores, where task lists can be assigned by the system.

Setting up the structure of the workers and responsibilities is an important task, and by doing it the right way this can save you form a lot of work.  The use of positions and jobs can ensure that the users get the correct level of access.  Let’s say we have the following retail organization shown in the next figure.

Here we have 2 stores, and it is relevant to ensure that the employees in one store only access the store they are working in.   We could model this hierarchy by assigning multiple address books to workers, customers and stores.

The workers can be connected to a position like “Store manager Bergen”.  The position is then connected to a Job like “Store manager”.  The job store manager can then be connected to a POS permission group.  Then you don’t need to individual POS permissions, but it is the position that decides what is allowed. 

Please spend time on this HR part, because it gives a lot of benefits when done properly.  And please add pictures of the employee.  It gives a more personal touch to the user😊

The permission group assigned to as job (or overridden on the worker) is the feature that is controlling what the worker is allowed to do in the POS. The fields are mostly self-explaining, but unfortunately not very well documented.

Here are some additional blogs on the subject.

Assign address books to customers, channels, and workers

Assigning address books to these records is easy.  Find the address book field, click on the lookup button and select the address books that the record should be a part of.

A small tip.  You cannot just copy/paste the address book values if you are marking the record with multiple address books.  You need to actually click on the lookup, and then select each of them.

Create email templates and email notification profiles

The email templates is located at Organization administration –> Setup –> Organization email templates.  The email template is can be defined per language.

If you click on the “edit” button there is an upload capability in the screen.  You also see a list of placeholders, where the system will fill in the specific information.  The exact placeholders available can be found here.

Here is a small, but valuable tip from me, that makes it easy to manually transfer your templates between installations.  Add the column “email”

Then a field with all the HTML is available for copy/paste.  Press CTRL-A to mark all contents, and then you can paste it into any HTML editor.  This is great if you want to just copy email templates from the Contoso demo data, and make some minor adjustments.

In a typical retail installation you would create quite a few email templates, and in the Contoso demo environment you can see a set that is relevant, and linked towards a commerce email notification profile. As you see here, there are emails for new order, confirmation, shipping, etc. You can also create separate emails per modes of delivery.

For configure the email batch, then the following docs is relevant to read.

Configure organizational hierarchies and hierarchy purposes

Organizational hierarchies are a powerful way of grouping a set of stores and then view and report from various perspectives.  I often make hierarchies based on reporting purposes and often mimic the hierarchy of the address books.  But you may also have geographical elements into the hierarchy.   Keep in mind that the levels in the hierarchy corresponds internal organizations of the party entity, and that the retail channel most often is the lowest level.  Therefore think through this setup carefully to ensure a correct structure.  Also take a look at the following video by André Arnaud de Calavon for more a valuable walkthrough of the feature. Remember that when you publish a hierarchy you select a data, and it is not allowed to make changes prior to this date.  I therefore recommend, that you publish the hierarchy on an earlier date, so that you have the possibility to make any corrections. 

The organizational hierarchies can be used a few places.  Like on the assortments where you can select what organizational entities should have a specific assortment.  You also use it for financial and transactional statement processing.  One that are relevant is the on the sales reporting, where the reporting is grouped according to the organizational hierarchy.

With some minor extensions it is possible to add additional levels, like region, franchisee etc, can be added by creating additional types of internal organizations.  I have done dis at a few customers with success 😊

Configure Commerce shared parameters

The shared parameters are common to all legal entities. And the most important setup here, is the number sequences and Identity providers.

Configure company-specific Commerce parameters

The commerce parameters are per legal entity, and contains the more specific setup and number sequences.  One important element is the “initialize” that creates the default configuration data.

Microsoft often have a set of configuration parameters for enabling features, like the “ProductSearch.UseAzureSearch”, that is essential when setting up the eCommerce.

The parameters here is actually not very well documented, and if often take some time “googling” or asking the community to find answers to each of the parameters.  But most of them should be self-explaining if you have been working with Dynamics 365 for a while.

Describe and configure additional functionality

Create and configure channel and sales order attributes

Attributes are documented here.  Channel attributes are attributes that are captured on the transactions that originates from the channel/store. These attributes can then again be used for information and reporting purposes. Lets say we want to record if the customer was happy when performing a purchase.  The first we need to do, is to create an attribute type:  

Then we create an attribute based on this attribute type.

I would then place the attribute into an attribute group, as I will probably later add more attributes I would like to record per sales order.

On the store/channel, I will add the happy group, and state that I would like to record this on the order header.

This will allow me record if the customer was happy when we performed the transaction. (Remember to run distribution job 1070 first)

When we then have performed a transaction, and run the P-job for importing the transactions to HQ, we can see the recorded attribute on the transaction.

As seen here, the attributes opens for many possibilities for recording information happening at your sales channel. Keep also in mind that when using call center, then the attributes also comes into play, and you can record attributes when creating the sales order.

Currently only simple strings are supported, but more types will be available in later releases.

 I hope you can see that the attributes in D365 is very flexible, and allows for a lot of scenarios.  I also see that the feature is underused in implementations, and hope that by using attributes we can avoid a lot of extensions related to data recording. 

Using attributes in power BI is also great for more depth analytics.

Configure commissions and sales representatives

Sales commission can be a nice way to reward hardworking employees, that manages to close the right deals.  The documentation is available here, and also take a look at the following blog for how to setup commission groups.  The way this works, is that when performing a sale, the sales order will be stamped with a sales representative, and on the sales group each sales representative can have a commission share.

I can then setup a commission calculation where I in this case give a commission of 2% on the revenue.

This will be posted to ledger according to the commission posting.

The process of paying out commissions to the sales representatives is not very well documented.  So, I guess the process is a bit manual, and solved by looking at breakdown on a sales order, click the invoice tab on the specified sales order and then select Invoice Journals, which will open a new form. In that new form, select Commission and click Commission transactions.

If you wat a list of all commission transactions, you may add the following to your D365 URL : “&mi=CommissionTrans” and this will then list up commissions per sales representative.

If you cannot see the menu item, it is because you have enabled the project operations integration at “Global project management and accounting parameters”.  It seams that there is a “collision” between the commission feature and the new project operations integration feature. I have no clue of why Microsoft have done this.

Configure payment methods and card types

The menu item for these are located at Retail and commerce à Channel setup à Payment methods.

Your start with defining the card types:

The next step is to define the card numbers, that is used to identify the card type based on the card number.

Payment methods lists up the acceptable payment methods. If you are looking for the Norwegian SAF-T cash register code you can find them here.

Configure payment methods and card types

The menu item for these are located at Retail and commerce –> Channel setup –> Payment methods.

Configure and manage gift cards

The menu items for gift cards is the following. In addition you have to define a service product that will be used when adding amounts to a card.

Configure and manage gift cards

The menu items for gift cards is the following. In addition you have to define a service product that will be used when adding amounts to a card.

The gift card is a number, balance

For gift cards, the following documentation gives some insight, especially if you need to integrate to an external gift card.  If a retailer’s operations are run entirely in D365, internal gift cards are the best solution. For complex retailers that span multiple countries or regions, and multiple point of sale (POS) systems, it’s often best to use a third party to manage gift card balances and enable gift cards to be used across those systems. The out-of-box payment connector for Adyen supports external gift cards through SVS and Givex in POS, the call center, and the e-commerce storefront.

Describe Omni-channel capabilities including payments, orders, and returns

BOPIS a term for buy online, pickup in store. The following omni-channel payment scenarios are supported:

  • Buy online, pick up in store
  • Buy in call center, pick up in store
  • Buy in store A, pick up in store B
  • Buy in store A, ship to customer

There is a lot to write about this, but lets show an example where we buy some snacks online, and pick it up in the store.  Here is my Vitalia site, where I have a snack.

When I click on this, I see that this item is available for pickup in store.

I select to pickup the item in the Bergen flagstore. Then I checkout

Then I can pickup this order in my CPOS:

I can then choose payment method, and the transaction is complete.  I even got some nice confirmation messages on email

Also checkout the omni-channel payments overview and  Payments FAQ for additional information on payment options in a omni-channel scenario.  Pay specially attention to Tokens that represent payment card numbers, payment authorizations, and previous payment captures. Tokens are important because they help keep sensitive data out of the point of sale (POS) system.

Configure data distribution

The database that stores data for a channel is separate from the Commerce database. The channel database holds only the data that is required for transactions. For example, master data is set up in Headquarters and then distributed to channels; on the other side of the transaction, transactional data is created in the point of sale (POS) or the online store and then uploaded to Headquarters. Microsoft have created an updated Commerce Data Exchange best practices that is quite new (15/7/2021), and discusses some nice topics worth exploring.  The following figure shows the flow of the distributions.

There is a set of data that require real-time direct access:

  • Issuing and redeeming gift cards
  • Redeeming loyalty points
  • Issuing and redeeming credit memos
  • Creating and updating customer records
  • Creating, updating, and completing sales orders
  • Receiving inventory against a purchase order or transfer order
  • Performing inventory counts
  • Retrieving sales transactions across stores and completing return transactions

Create info codes, sub-codes, and info code groups

Info codes are used to capture additional information behind actions that occur in the POS and call center Commerce channel. Depending on the input type, users can assign various limitations and restrictions for certain info code types. Some info codes can require input, only trigger once for each transaction (regardless of products), link multiple info codes together, and more.

Describe Dynamics 365 Fraud Protection purchase protection, loss prevention, and account protection

The following image shows several examples of what type of fraud can occur at different phases in the customer journey.

Fraud Protection offers three capabilities that can be integrated together or used individually, which provides merchants with the option to use the capability that best suits their business needs.  Here is a picture of how the application looks like.

Purchase Protection – Helps merchants preserve genuine purchases and decrease fraud. It helps protect online revenue by improving the acceptance rates of commerce transactions with insights and tools that help balance revenue opportunity versus fraud loss and checkout friction.

Account Protection – Helps merchants combat account creation and account takeover fraud. It helps improve customer experience at critical steps of the account life cycle by enabling merchants to block fraudulent activities and protect their customers’ accounts.

Loss Prevention – Helps protect revenue by identifying anomalies and potential fraud that are affecting returns and discounts that arise from omnichannel purchases, enabling store managers and loss prevention officers to quickly take action to mitigate losses.

Manage statements

Describe advantages of using trickle feed-based posting

With trickle feed-based order creation, transactions are processed throughout the day, and only the financial reconciliation of tenders and other cash management transactions are processed at the end of the day. This functionality splits the load of creating sales orders, invoices, and payments throughout the day, providing better perceived performance and the ability to recognize revenue and payments in the books in near real-time.

See also the following blog-post.

Validate retail transactions by using the transaction consistency checker

When a statement is posted, posting can fail due to inconsistent data in the commerce transaction tables. The data issue may be caused by unforeseen issues in the point of sale (POS) application, or if transactions were incorrectly imported from third-party POS systems. Examples of how these inconsistencies may appear include:

  • The transaction total on the header table does not match the transaction total on the lines.
  • The line count on the header table does not match with the number of lines in the transaction table.
  • Taxes on the header table do not match the tax amount on the lines.

Transactions that fail the validation check and transactions that have not yet been validated will not be pulled into statements. During the “Calculate statement” process, users will be notified if there are transactions that could have been included in the statement but weren’t. If a validation error is found, there is a capability so that users can fix the records that failed through the user interface. Logging and auditing capabilities will also be made available to trace the history of the modifications.

Configure and manage retail statement calculations and posting

The statement posting process uses the distribution schedule to pull a set of POS transactions into the headquarters (HQ) client. The following illustration shows the statement posting process. In this process, transactions that are recorded in the POS are transmitted to the client by using the Commerce scheduler. After the client receives the transactions, you can create, calculate, and post the transaction statement for the store.

When I set up these I normally schedule them as batch jobs

Troubleshoot statement posting issues

When posting retail statements, there is a lot of checks to ensure that the transactions are correctly posted. In addition to the retail transaction consistency check, we often see issues that is common with invoice updating a sales order.  This involves that the inventory posting is setup correctly, currency rounding, financial dimensions etc.  I have also several times encountered issues related to the fact that the inventory is closed when the transactions are imported.  Most of them can be fixed from within the D365 application.  The posting error should in most cases look like this:

Источник: https://kurthatlevik.com/

About Cryptolens

Cryptolens is a cloud-based licensing as a service (LaaS) platform, which helps organizations manage licenses for mobile and desktop applications, embedded systems and plug-ins. Features include offline activation, price optimization, reseller portals, template management. The application allows administrators to implement various licensing models such as subscription, perpetual, pay-per-use or floating, restrict feature usage for specific members and monitor the expiration date. The AI-based platform enables businesses to define the value of product for each customer. Cryptolens includes a messaging API, which helps broadcast messages across systems and notify about new updates. With its analytics module, administrators can determine application usage and detect unauthenticated users in real-time. Cryptolens offers integration with various third-party platforms such as Stripe, Sendowl and PayPal. Pricing is based on actual usage computed on a monthly basis and support is provided via email and documentation.

Cryptolens pricing

Cryptolens does not have a free version but does offer a free trial. Cryptolens paid version starts at USD 10.00/month.

Starting Price:

USD 10.00/month

Pricing Details:

The pricing model is based on actual usage computed monthly.

Alternatives to Cryptolens

View all alternatives

Cryptolens Reviews

1 review View all reviews

  • Industry: Information Technology & Services
  • Company size: 11-50 Employees
  • Used Weekly for 2+ years
  • Review Source

Amazing license management tool

We have an on premise email parsing assembly that needed licensing wrapped around it. We thought about doing it ourselves but that seemed really messy and error prone. It took about a week of development to get Cyrptolens fully integrated into our build process and our code base but it has been a huge time saver for us. When we have customers who need to purchase we just direct them to our Cryptolens portal where the person can setup an account and purchase and get their license key.

Pros

- Super simple setup.
- Great documentation.
- Support has been amazing.
- Great billing software integration with Stripe.
- Good .NET support
- Portal for customers to purchase from simplifies license management a lot

Cons

- The .NET nuget package from Cryptolens isn't obfuscated so we had to handle that ourselves.

Response from Cryptolens

Thank you so much for your feedback, Paul!

Replied 13/04/2021

Related categories

Источник: https://www.softwareadvice.com.au/software/111090/cryptolens

Comarch Real-time Network Inventory Management stores complete information about physical, logical and virtual network resources. It is a shared, central fixed-access inventory to capture all details of a very complex IT/telecom environment with advanced micro-services technology underneath.

Telecom Real-time Network Inventory facilitates network resource catalog management for multi-vendor, multi-domain networks. It manages RAN, transmission, core, and fixed network domains, IT infrastructure and data center inventory tasks for SDN/NFV and hybrid networks, handling both inside plant telecom and outside plant telecom operations, and allowing easy onboarding of new technologies.

With artificial intelligence Comarch Real-time Network Inventory supports the management of the end to end network, while enabling automation within each dynamic virtual domain based on immediately available network resources. Static physical and logical resources are managed by the conventional Comarch Network Inventory Management software. Comarch Real-time Network inventory with AI manages the dynamic virtual resources.

Network Inventory Data can be also accessed via the OSS Mobile App (iOS and Android devices) by technician performing tasks on the site. Efficient task handling in a highly-paced 5G environment requires more support and data access for field technicians. The Comarch OSS Mobile App enables technicians to access network inventory data and process their field activities while on the site. A technician can browse the physical and logical structure of network elements during a site audit or while undertaking hardware modifications. The app provides the possibility to quickly add active and passive devices on-site and provides access to a knowledge base with devices on-site accessible in the most convenient way, by using augmented reality features.

Press Release: Real-time Network Inventory Management of the Arqiva Network and Service:

arqiva, network resource management

Comarch, a global supplier of software and services, provides the Operational Support System (OSS) and professional services that supports Arqiva’s smart metering platform, part of the UK Government’s Smart Metering Programme that will be delivered to 26 million homes in the UK by 2020...

Read more now >>

The Use Of AI and ML for Automated Cross Vendor VNF Self Healing and Auto Scaling

Watch our video!

End to end view of multi-vendor, multi-technology networks

The idea is to represent the same equipment and connections in several layers, with technology-specific information included in the dedicated-generic layer providing a consistent view of the network for the operator, without an information overflow.

Improved utilization of existing resources

An up to date, cross-domain network inventory management is the basis of network investments in telecoms. It allows the efficient utilization of existing resources, and planning of new ones which are profitable from the business perspective.

Reduced network operating cost

Having one consistent view of the network for all technologies and layers allows the operator to increase business efficiency and decrease operational costs. Inventory is the foundation of a lot of business processes across a telecom company, including the network operation center, engineering and planning departments, procurement, and business partners.

Integrated in umbrella OSS

Resource & Network Inventory is the heart of Comarch OSS. It provides the data and information for all other modules, such as Planning & Design, Configuration Management, Fault Management, Service Quality Management, Customer Experience Management, and Business Process Management. All dedicated modules utilize the same inventory database, which leads to efficient data processing and, thanks to the elimination of lots of dedicated interfaces, reduced operational costs.

Efficient resources assurance

Comarch Network Inventory provides a network assurance system support with topological correlations and allows recognition and troubleshooting of the root cause of failures in the most efficient manner.

Innovations

Thanks to its future-proof architecture, Comarch OSS is already integrated with the NFV/SDN framework in the inventory, planning, configuration and assurance areas. This means that the Comarch OSS is an umbrella OSS for new virtualized and legacy architectures.

Mobile access

Secured and instant access to network inventory data from mobile device improves the way of executing site surveys and keeping physical site information data up to date.

The Successful Rollout of 5G Base Stations with Comarch OSS

Watch our video!

See Comarch Real-time Network Inventory Management Product in Use. Read Customer References:

Browse Our PDF Materials Related to Network Resource Management in Telecom!

See all resources

Need some help with product selection?

Tell us about your business needs. We will find the perfect product for your challenge.

Contact Us

Our site uses cookies to better meet your requirements. Proper configuration of browser options allows you to block or remove cookies but can also cause the site to not function properly or even at all. By continuing to use the site, with no change to your browser settings, you agree to the use of cookies. We changed our Privacy Policy for cookies and other similar technologies.
Learn more.

Источник: https://www.comarch.com/telecommunications/oss-solutions/network-inventory-management/
Market-Inspector". www.epossystemsguide.co.uk (in Danish). Retrieved 2016-05-03.
  • ^Frazier, Bob (October 16, 2013). "Restaurant POS 3-Step Purchase Process". Newswire. Retrieved February 15, 2014.
  • ^"How hackers gave Subway a $3 million lesson in point-of-sale security". Ars Technica. Retrieved 15 October 2017.
  • ^Seals, Tara (13 June 2016). "Wendy's Point of Sale Hack Grows Bigger". Infosecurity. Retrieved 15 October 2017.
  • ^"SAP point-of-sale systems were totally hackable with $25 kit". The Register. 29 August 2017.
  • ^"SAP POS Flaw Allows Hackers to Change Pricing". Infosecurity. 25 August 2017.
  • ^"Security Bug Affects Over 300,000 Oracle POS Systems". Catalin Cimpanu. 31 January 2018. Retrieved 31 January 2018 – via BleepingComputer.
  • External links[edit]

    Источник: https://en.wikipedia.org/wiki/Point_of_sale

    B2B eCommerce Platform

    A Few Words From Our Clients

    Cornelius Munz   Digital Solution Engineer

    Here at Bosch Thermotechnik we were looking for a 100% customizable .NET eCommerce platform with superior support options. We had an objective of launching a marketplace loyalty platform that will function smoothly in 25 countries. Eventually, by choosing Virto Commerce we successfully launched the platform, our clientele has become more engaged, and we have increased the turnover. 

    — Cornelius Munz   Digital Solution Engineer

    Richard Birksteiner

    The value of the Virto Commerce scalable platform has been huge for us as a partner, specifically in enabling us to craft a flexible B2B solution without short- and long-term limitations. Virto Commerce has been a great partner for us because they are ready to deliver all B2B scenarios and out-of-the-box technologies that we need.

    — Richard Birksteiner
    Chief Technology Officer, rb2

    Andreas Kardell

    We only adopt technologies that easily enable new business channels, flexibly customize product catalogs, and accurately track overall sales performance and Virto Commerce solves all of these.

    — Andreas Kardell CTO at Proffsmagasinet.se

    Michael Theebe

    Virto Commerce was the best fit for De Klok Dranken as it combined cost-effectiveness with the functionality, flexibility, and scalability – today and in the long term.

    — Michael Theebe Marketing and ecommerce Manager at De Klok Dranken

    Isaac Barnes

    We chose Virto Commerce for the Executive Office of the US Government supply chain solution because it is the only platform that could meet our business user requirements to provide the modern ecommerce shopping experience we wanted, as well as the technical requirements of being customizable, flexible, secure, open source and built on a Microsoft .NET technology stack.

    — Isaac Barnes Vice President, Eminent IT

    Group CTO for Giift.com

    Thanks to its headless architecture and next-generation features, Virto Commerce has helped us completely rebuild our marketplace solution. Our Virto Commerce Catalog now covers all our complex marketplace scenarios and has materially increased end User eXperience, unlocked new revenue and decreased maintenance cost. Using GraphQL and Elastic Search is just awesome!

    — Philippe Stephan Group CTO for Giift.com

    Stijn De Vos Lead Expert at delaware

    Delaware partnered with Virto Commerce in order to ensure true scalability for our client Standaard Boekhandel. We have easily extended the product offering and improved the search functionality for their two brands. In short, we found a .NET eCommerce platform that is capable of processing a product catalog of over 15 million products and customer orders in 207 fulfillment centers without any hurdle.

     — Stijn De Vos  Lead Expert at delaware

    Want a quick demo?

    Let's talk:

    Adam Willmouth, Sales Director, America

    Alain Van Hove, Sales Director, EMEA

    Источник: https://virtocommerce.com/

    General benefits

    Microsoft have released a new exam for the Commerce functional consultant.  I did take this exam in the beginning of July, and it can take a few weeks before the results come.  But I’m pretty sure I will fail.  The exam was quite hard and there was just too little time. I got 62 questions, but only managed to answer approx. 45 of them within the timeframe of 90 minutes.  If you think MB-300 was difficult, then MB-340 is harder!

    This blogpost is therefore my study notebook to retake the exam(if I fail😊).  You will not find any of the exam questions or answers here, but if you follow this steps, I think you will be closer to achieving your goal of passing the MB-340 exam, and also to understand the topic better.  The chapter and headlines are organized accoring to the skills measured list of MB-340.

    Disclaimer:  Some texts and pictures are copied from the Microsoft learn, docs. demo environments and other sites.  In most cases you should find a hyperlink to the original source for a deeper study, and there are no guaranties that all here is right.  You should always refer to the official Microsoft documentation and training.

    Enjoy and god luck studying.

    Configure prerequisites and commerce parameters

    Create employee and customer address books

    Employee and customer address books are used to limit the personal to specific stores/POS or what information the employee should be see in HQ.  How to create an address book is documented here. One nice feature here is that the address book is the basis for the extensible data security (XDS) policy, that limits what stores and transactions a HQ user can access.  To make the XDS to work, remember to assign the correct Retail* roles to the users.  This will ensure that the address book filtering is working as expected.

    What I normally recommend is to have one address book per store, one for the region, one global address book and one address book for customers.  If there are multiple brands, I also have customer address book for this.  Keep in mind that you can select multiple address books towards stores, employees, and customers.  I also like to think of address books as a hierarchy, and this allows for ensuring that regional managers can see their information and transactions across stores, while a store clerk only see information relevant to his job.     

    Configure and manage retail workers

    Retail workers are setup using features from the HR features, but the workers table is accessible from the retail menu.  Commerce lets you perform the following employee management functions:

    • Create entities for jobs, positions, and workers
    • Assign workers to more than one store
    • Configure different language settings for each user and user-based POS screen layouts
    • Limit the list of allowed operations

    Additionally, you can configure the POS permission groups to associate different employees with different roles. The task management feature offers productivity enhancements for employees at the stores, where task lists can be assigned by the system.

    Setting up the structure of the workers and responsibilities is an important task, and by doing it the right way this can save you form a lot of work.  The use of positions and jobs can ensure that the users get the correct level of access.  Let’s say we have the following retail organization shown in the next total network inventory demo - Activators Patch src="https://kurthatlevik.files.wordpress.com/2021/08/image2-1.png?w=1381" alt="">

    Here we have 2 stores, and it is relevant to ensure that the employees in one store only access the store they are working in.   We could model this hierarchy by assigning multiple address books to workers, customers and stores.

    The workers can be connected to a position like “Store manager Bergen”.  The position is then connected to a Job like “Store manager”.  The job store manager can then be connected to a POS permission group.  Then you don’t need to individual POS permissions, but it is the position that decides what is allowed. 

    Please spend time on this HR part, because it gives a lot of benefits when done properly.  And please add pictures of the employee.  It gives a more personal touch to the user😊

    The permission group assigned to as job (or overridden on the worker) is the feature that is controlling what the worker is allowed to do in the POS. The fields are mostly self-explaining, but unfortunately not very well documented.

    Here are some additional blogs on the subject.

    Assign address books to customers, channels, and workers

    Assigning address books to these records is total network inventory demo - Activators Patch Find the address book field, click on the lookup button and select the address books that the record should be a part of.

    A small tip.  You cannot just copy/paste the address book values if you are marking the record with multiple address books.  You need to actually click on the lookup, and then select each of them.

    Create email templates and email notification profiles

    The email templates is located at Organization administration –> Setup –> Organization email templates.  The email template is can be defined per language.

    If you click on the “edit” button there is an upload capability in the screen.  You also see a list of placeholders, where the system will fill in the specific information.  The exact placeholders available can be found here.

    Here is a small, but valuable tip from me, that makes it easy to manually transfer your templates between installations.  Add the column “email”

    Then a field with all the HTML is available for copy/paste.  Press CTRL-A to mark all contents, and then you can paste it into any HTML editor.  This is great if you want to just copy email templates from the Contoso demo data, and make some minor adjustments.

    In a typical retail installation you would create quite a few email templates, and in the Contoso demo environment you can see a set that is relevant, and linked towards a commerce email notification profile. As you see here, there are emails for new order, confirmation, shipping, etc. You can also create separate emails per modes of delivery.

    For configure the email batch, then the following docs is relevant to read.

    Configure organizational hierarchies and hierarchy purposes

    Organizational hierarchies are a powerful way of grouping a set of stores and then view and report from various perspectives.  I often make hierarchies based on reporting purposes and often mimic the hierarchy of the address books.  But you may also have geographical elements into the hierarchy.   Keep in mind that the levels in the hierarchy corresponds internal organizations of the party entity, and that the retail channel most often is the lowest level.  Therefore think through this setup carefully to ensure a correct structure.  Also take a look at the following video by André Arnaud de Calavon for more a valuable walkthrough of the feature. Remember that when you publish a hierarchy you select a data, and it is not allowed to make changes prior to this date.  I therefore recommend, that you publish the hierarchy on an earlier date, so that you have the possibility to make any corrections. 

    The organizational hierarchies can be used a few places.  Like on the assortments where you can select what organizational entities should have a specific assortment.  You also use it for financial and transactional statement processing.  One that are relevant is the on the sales reporting, where the reporting is grouped according to the organizational hierarchy.

    With some minor extensions it is possible to add additional levels, like region, franchisee etc, can be added by creating additional types of internal organizations.  I have done dis at a few customers with success 😊

    Configure Commerce shared parameters

    The shared parameters are common to all legal entities. And the most important setup here, is the number sequences and Identity providers.

    Configure company-specific Commerce parameters

    The commerce parameters are per legal entity, and contains the more specific setup and number sequences.  One important element is the “initialize” that creates the default configuration data.

    Microsoft often have a set of configuration parameters for enabling features, like the “ProductSearch.UseAzureSearch”, that is essential when setting up the eCommerce.

    The parameters here is actually not very well documented, and if often take some time “googling” or asking the community to find answers to each of the parameters.  But most of them should be self-explaining if you have been working with Dynamics 365 for a while.

    Describe and configure additional functionality

    Create and configure channel and sales order attributes

    Attributes are documented here.  Channel attributes are attributes that are captured on the transactions that originates from the channel/store. These attributes can then again be used for information and reporting purposes. Lets say we want to record if the customer was happy when performing a purchase.  The first we need to do, is to create an attribute type:  

    Then we create an attribute based on this attribute type.

    I would then place the attribute into an attribute group, as I will probably later add more attributes I would like to record per sales order.

    On the store/channel, I will add the happy group, and state that I would like to record this on the order header.

    This will allow me record if the customer was happy when we performed the transaction. (Remember to run distribution job 1070 first)

    When we then have performed a transaction, and run the P-job for importing the transactions to HQ, we can see the recorded attribute on the transaction.

    As seen here, the attributes opens for many possibilities for recording information happening at your sales channel. Keep also in mind that when using call center, then the attributes also comes into play, and you can record attributes when creating the sales order.

    Currently only simple strings are supported, but more types will be available in later releases.

     I hope you can see that the attributes in D365 is very flexible, and allows for a lot total network inventory demo - Activators Patch scenarios.  I also see that the feature is underused in implementations, and hope that by using attributes we can avoid a lot of extensions related to data recording. 

    Using attributes in power BI is also great for more depth analytics.

    Configure commissions and sales representatives

    Sales commission can DVDFab 10.0.9.5 Crack + Keygen Full Version Download a nice way to reward hardworking employees, that manages to close the right deals.  The documentation is available here, and also take a look at the following blog for how to setup commission groups.  The way this works, is that when performing a sale, the sales order will be stamped with a sales representative, and on the sales group each sales representative can have a commission share.

    I can then setup a commission calculation where I in this case give a commission of 2% total network inventory demo - Activators Patch the revenue.

    This will be posted to ledger according to the commission posting.

    The process of paying out commissions to total network inventory demo - Activators Patch sales representatives is not very well documented.  So, I guess the process is a bit manual, and solved by looking at breakdown on a sales order, click the invoice tab on the specified sales order and then select Invoice Journals, which will open a new form. In that new form, select Commission and click Commission transactions.

    If you wat a list of all commission transactions, you may add the following to your D365 URL : “&mi=CommissionTrans” and this will then list up commissions per sales representative.

    If you cannot see the menu item, it is because you have enabled the project operations integration at “Global project management and accounting parameters”.  It seams that there is a “collision” between the commission feature and the new project operations integration feature. I have no clue of why Microsoft have done this.

    Configure payment methods and card types

    The menu item for these are located at Retail and commerce à Channel setup à Payment methods.

    Your start with defining the card types:

    The next step is to define the card numbers, that is used to identify the card type based on the card number.

    Payment methods lists up the acceptable payment methods. If you are looking for the Norwegian SAF-T cash register code you can find them here.

    Configure payment methods and card types

    The menu item for these are located at Retail and commerce –> Channel setup –> Payment methods.

    Configure and manage gift cards

    The menu items for gift cards is the following. In total network inventory demo - Activators Patch you have to define a service product that will be used when adding amounts to a card.

    Configure and manage gift cards

    The menu items for gift cards is the following. In addition you have to define a service product that will be used when adding amounts to a card.

    The gift card is a number, balance

    For gift cards, the following documentation gives some insight, especially if you need to integrate to an external gift card.  If a retailer’s operations are run entirely in D365, internal gift cards are the best solution. For complex retailers that span multiple countries or regions, and multiple point of sale (POS) systems, it’s often best to use a third party to manage gift card balances and enable gift cards to be used across those systems. The out-of-box payment connector for Adyen supports external gift cards through SVS and Givex in POS, the call center, and the e-commerce storefront.

    Describe Omni-channel capabilities including payments, orders, and returns

    BOPIS a term for buy online, pickup in store. The following omni-channel payment scenarios are supported:

    • Buy online, pick up in store
    • Buy in call center, pick up in store
    • Buy in store A, pick up in store B
    • Buy in store A, ship to customer

    There is a lot to write about this, but lets show an example where we buy some snacks online, and pick it up in the store.  Here is my Vitalia site, where I have a snack.

    When I click on this, I see that this item is available for pickup in store.

    I select to pickup the item in the Bergen flagstore. Then I checkout

    Then I can pickup this order in my CPOS:

    I can then choose payment method, and the transaction is complete.  I even got some nice confirmation messages on email

    Also checkout the omni-channel payments overview and  Payments FAQ for additional information on payment options in a omni-channel scenario.  Pay specially attention to Tokens that represent payment card numbers, payment authorizations, and previous payment captures. Tokens are important because they help keep sensitive data out of the point of sale (POS) system.

    Configure data distribution

    The database that stores data for a channel is separate from the Commerce database. The channel database holds only the data that is required for transactions. For example, master data is set up in Headquarters and then distributed to channels; on the other side of the transaction, transactional data is created in the point of sale (POS) or the online store and then uploaded to Headquarters. Microsoft have created an updated Commerce Data Exchange best practices that is quite new (15/7/2021), and discusses some nice topics worth exploring.  The following figure shows the flow of the distributions.

    There is a set of data that require real-time direct access:

    • Issuing and redeeming gift cards
    • Redeeming loyalty points
    • Issuing and redeeming credit memos
    • Creating and updating customer records
    • Creating, updating, and completing sales orders
    • Receiving inventory against a purchase order or transfer order
    • Performing inventory counts
    • Retrieving sales transactions across stores and completing return transactions

    Create info codes, sub-codes, and info code groups

    Info codes are used to capture additional information behind actions that occur in the POS and call center Commerce channel. Depending on the input type, users can assign various limitations and restrictions for certain info code types. Some info codes can require input, only trigger once for each transaction (regardless of products), link multiple info codes together, and more.

    Describe Dynamics 365 Fraud Protection purchase protection, loss prevention, and account protection

    The following image shows several examples of what type of fraud can occur at different phases in the customer journey.

    Fraud Protection offers three capabilities that can be integrated together or used individually, which provides merchants with the option to use the capability that best suits their business needs.  Here is a picture of how the application looks like.

    Purchase Protection – Helps merchants preserve genuine purchases and decrease fraud. It helps protect online revenue by improving the acceptance rates of commerce transactions with insights and tools that help balance revenue opportunity versus fraud loss and checkout friction.

    Account Protection – Helps merchants combat account creation and account takeover fraud. It helps improve customer experience at critical steps of the account life cycle by enabling merchants to block fraudulent activities and protect their customers’ accounts.

    Loss Prevention – Helps protect revenue by identifying anomalies and potential fraud that are affecting returns and discounts that arise from omnichannel purchases, enabling store managers and loss prevention officers to quickly take action to mitigate losses.

    Manage statements

    Describe advantages of using trickle feed-based posting

    With trickle feed-based order creation, transactions are processed throughout the day, and only the financial reconciliation of tenders total network inventory demo - Activators Patch other cash management transactions are processed at the end of the day. This functionality splits the load of creating sales orders, invoices, and payments throughout the day, providing better perceived performance and the ability to recognize revenue and payments in the books in near real-time.

    See also the following blog-post.

    Validate retail transactions by using the transaction consistency checker

    When a statement is posted, posting can fail due to inconsistent data in the commerce transaction tables. The data issue may be caused by unforeseen issues in the point of sale (POS) application, or if transactions were incorrectly imported from third-party POS systems. Examples of how these inconsistencies may appear include:

    • The transaction total on the header table does not match the transaction total on the lines.
    • The line count on the header table does not match with the number of lines in the transaction table.
    • Taxes on the header table do not match the tax amount on the lines.

    Transactions that fail the validation check and transactions that have not yet been validated will not be pulled into statements. During the “Calculate statement” process, users will be notified if there are transactions that could have been included in the statement but weren’t. If a validation error is found, there is a capability so that users can fix the records that failed through the user interface. Logging and auditing capabilities will also be made available to trace the history of the modifications.

    Configure and manage retail statement calculations and posting

    The statement posting process uses the distribution schedule to pull a set of POS transactions into the headquarters (HQ) client. The following illustration shows the statement posting process. In this process, transactions that are recorded in the POS are transmitted to the client by using the Commerce scheduler. After the client receives the transactions, you can create, calculate, and post the transaction statement for the store.

    When I total network inventory demo - Activators Patch up these I normally schedule them as batch jobs

    Troubleshoot statement posting issues

    When posting retail statements, there is a lot of checks to ensure that the transactions are correctly posted. In addition to the retail transaction consistency check, we often see issues that is common with invoice updating a sales order.  This involves that the inventory posting is setup correctly, currency rounding, financial dimensions etc.  I have also several times encountered issues related to the fact that the inventory is closed when the transactions are imported.  Most of them can be fixed from within the D365 application.  The posting error should in most cases look like this:

    Источник: https://kurthatlevik.com/

    About Cryptolens

    Cryptolens is a cloud-based licensing as a service (LaaS) platform, which helps organizations manage licenses for mobile and desktop applications, embedded systems and plug-ins. Features include offline activation, price optimization, reseller portals, template management. The application allows administrators to implement various licensing models such as subscription, perpetual, pay-per-use or floating, restrict feature usage for specific members and monitor the expiration date. The AI-based platform enables businesses to define the value of product for each customer. Cryptolens includes a messaging API, which helps broadcast messages across systems and notify about new updates. With its analytics module, administrators can determine application usage and detect unauthenticated users in real-time. Cryptolens offers integration with various third-party platforms such as Stripe, Sendowl and PayPal. Pricing is based on actual usage computed on a monthly basis and support is provided via total network inventory demo - Activators Patch and documentation.

    Cryptolens pricing

    Cryptolens does not have a free version but does offer a free trial. Cryptolens paid version starts at USD 10.00/month.

    Starting Price:

    USD 10.00/month

    Pricing Details:

    The pricing model is based on actual usage computed monthly.

    Alternatives to Cryptolens

    View all alternatives

    Cryptolens Reviews

    1 review View all reviews

    • Industry: Information Technology & Services
    • Company size: 11-50 Employees
    • Used Weekly for 2+ years
    • Review Source total network inventory demo - Activators Patch

    Amazing license management tool

    We have an on premise email parsing assembly that needed licensing wrapped around it. We thought about doing it ourselves but that seemed really messy and error prone. It took about a Format Factory 4.3.0.0 Crack + Serial Key Download Full of development to get Cyrptolens fully integrated into our build process and our code base but it has been a huge time saver for us. When we have customers who need to purchase we just direct them to our Cryptolens portal where the person can setup an account and purchase and get their license key.

    Pros

    - Super simple setup.
    - Great documentation.
    - Support has been amazing.
    - Great billing software integration with Stripe.
    - Good .NET support
    - Portal for customers to purchase from simplifies license management a lot

    Cons

    - The .NET nuget package from Cryptolens isn't obfuscated so we had to handle that ourselves.

    Response from Cryptolens

    Thank you so much for your feedback, Paul!

    Replied 13/04/2021

    Related categories

    Источник: https://www.softwareadvice.com.au/software/111090/cryptolens
    Market-Inspector". www.epossystemsguide.co.uk (in Danish). Retrieved 2016-05-03.
  • ^Frazier, Bob (October 16, 2013). "Restaurant POS 3-Step Purchase Process". Newswire. Retrieved February 15, 2014.
  • ^"How hackers gave Subway a $3 million lesson in point-of-sale security". Ars Technica. Retrieved 15 October 2017.
  • ^Seals, Tara (13 June 2016). "Wendy's Point of Sale Hack Grows Bigger". Infosecurity. Retrieved 15 October 2017.
  • ^"SAP point-of-sale systems were totally hackable with $25 kit". The Register. 29 August 2017.
  • ^"SAP POS Flaw Allows Hackers to Change Pricing". Infosecurity. 25 August 2017.
  • ^"Security Bug Affects Over 300,000 Oracle POS Systems". Catalin Cimpanu. 31 January 2018. Retrieved 31 January 2018 – via BleepingComputer.
  • External links[edit]