Last year I was creating an interface for products and their attributes. The funny thing was that the attributes did not appear in the interface, but on opening the form, all the attributes were there. So one begins to think what is going on! Where are my missing attributes? To get to the bottom of […]
The post Products with missing attributes appeared first on Kaya Consulting.
Si estáis trabajando con la primera versión de Dynamics 365 for Operations Update 3, al intentar compilar nuestro aplicativo vía Visual Studio Online nos encontraremos con el siguiente error:
2016-11-09T16:38:25.5277020Z VERBOSE: 4:38:25 PM: – Backup completed with RoboCopy exit code: 1.
2016-11-09T16:38:45.0277150Z VERBOSE: 4:38:45 PM: – Backup contains 5267623892 bytes in 193683 files:
2016-11-09T16:38:45.0277150Z I:\DynamicsBackup\Packages
2016-11-09T16:38:45.0277150Z WARNING: 4:38:45 PM: – Backup size does not match deployment metadata size
2016-11-09T16:38:45.0277150Z (Backup: 5267623892 bytes, Deployment metadata: 5267031092 bytes).
2016-11-09T16:38:45.0589660Z VERBOSE: 4:38:45 PM: – Exception thrown at
2016-11-09T16:38:45.0589660Z C:\DynamicsSDK\PrepareForBuild.ps1:261: throw “Failed to create backup of
2016-11-09T16:38:45.0589660Z metadata packages.”
2016-11-09T16:38:45.0589660Z
2016-11-09T16:38:45.0589660Z System.Management.Automation.RuntimeException: Failed to create backup of
2016-11-09T16:38:45.0589660Z metadata packages.
2016-11-09T16:38:45.1527190Z ##[error]Write-Message : 4:38:45 PM: Error preparing build environment: Failed to
create backup of metadata packages.
Siendo totalmente imposible compilar nuestro aplicativo.
Siempre que intentamos programar la compilación nos encontramos que el script de realizar el backup de nuestro código falla, dando un tamaño diferente entre origen y destino.
Esto es debido a un error en el script de copia, donde el script de Powershell al copiar la carpeta J:\AosService\PackagesLocalDirectory para hacer un backup, está copiando el contenido de un Symlink en lugar del link
Podéis encontrar más información en el siguiente link de lcs https://fix.lcs.dynamics.com/Issue/Resolved/?kb=3205627
Para arreglar el problema, podemos instalar el hotfix facilitado por Microsoft o agregar nostros el parámetro /SL en el script de copia, para ello nos conectaremos por terminal server a nuestro servidor y buscaremos la siguiente ruta: c:\DynamicsSDK el archivo PrepareForBuild.ps1
Editamos el fichero y agregamos el parámetro /SL en la siguiente sentencia:
$Output = & RoboCopy $DeploymentPackagesPath $BackupPath /MIR /COPYALL /E /R:3 /W:10 /NFL /NDL /NS /NC /NP /SL /LOG:”$RoboCopyLog”
Following are some recommendation.
You don’t have to be working in the IT/CS these days in order for your ears (or eyes) to pick up the term Machine Learning (ML) or Data Science, since these are among the biggest tech trends nowadays. Machine Learning, being the subset of Artificial Intelligence (some of you might disagree with this) is a concept ubiquitous in our daily lives.
If you are using a Personal Assistant such as Cortana, Siri or Google Now– as soon as you wake up, you can get information such as which traffic route to take to work, based on previous trends and patterns in traffic, or if you’re using any of the Fitness Trackers – it can learn your sleeping habits and pick an ideal time for waking up. Fast-forward through the day – as you are surfing the web – big tech giants are collecting your information and by comparing your habits to other people and their interests – and it can target you surprisingly well with ads and recommendations that suit your needs. After long working day, in not so distant future, most of all us will have a large number of sensors laid out at home, sending data to Cloud in order for a ML system to pick up our evening routines and automate heating systems, lighting, and we’ll see what else. Or – if you are inpatient – take a look at I.T. (2016) movie :).
This is not something revolutionary new, we have these concepts around for quite some time now. And those are so omnipresent that the industry needs more and more people working with ML everyday to fulfill the business needs. But Machine Learning is hard. The field is still young, research papers are published daily and it’s a combination of Statistics and Probability, Mathematics and Computer Science for the most part. In order to start from scratch and understand the underpinning of various algorithms used, and optimize them and scale effectively, you’ll need a scientific background and even probably a PhD in some of the quantitative fields.
Luckily, the ecosystem matures and we see a trend of democratization of Machine Learning and this is where Microsoft and their research team is brining a new way for developers and engineers without a ML background to take advantage of breakthroughs in the field. We’ll see how we can jump the train and be a part of the revolution brought by Microsoft and their Azure cloud platform.
Azure Machine Learning Studio is a GUI-based integrated development environment for constructing and operationalizing Machine Learning workflow on Azure.
Let’s go through the basic workflow of Azure ML:
The basic cycle is as follows: Collect -> Analyze/Model -> Consume.
The first, and probably most time consuming step is to collect the data you need in order to train your model. We’ll talk more about this later, but the point is data is often unorganized, incomplete or even conflicting. Fortunately, Azure ML Studio has a large number of tools to help you with that. Once we get our data right in sense of magnitude and correctness, we need to select the proper algorithm for model training. There are both supervised and unsupervised algorithms available from the regression, classification, clustering and anomaly detection families. Finally, after you pick your algorithm you need to evaluate and test your model. Usually, you’ll split your collected data into training, validation and test sets which you will use to train and test your model, respectively. Again, Azure ML Studio gives you support for that, and we’ll see this in one of the coming blogs.
The final result is – you have your (hopefully) well trained model, which you can use to predict outputs based on inputs that were not in your original data set. And this is where Azure ML Studio really shines – with a couple of clicks you can add intelligence to your (mobile) apps, websites or provide insights in BI tools such as Power BI or Microsoft Excel. This is done by adding a web service which acts as an interface between your model and client apps – web service can be invoked with a single request-response model, or it can be batched.
Download full diagram here.
The only thing you need in order to use Azure Machine Learning Studio is a Microsoft account. You get:
So, go ahead and create an account on https://studio.azureml.net, and the next blog will follow with end to end instructions how can we create and integrate data intelligence in our client apps. Stay tuned!
The post Intro To (Azure) Machine Learning – Part 1 appeared first on Merit Solutions.
During project build process following operations are performing. All these operations are one by one after each other.
 |
| Imagine I am running this today to clean up everything older than three weeks in EventInbox. |
When making an adjustment for a Project Expense where you are changing a dimension you might encounter an error message that says
‘Account number for transaction type Ledger journal does not exist’
‘Posting has been cancelled’
once you post the adjustment
If you receive this message, try to go to Project Management and Accounting\Setup\Posting\Default offset accounts for expenses and note if you have specified any account here. If it is not the case, enter an account for the desired combination and try to see if you can not do your adjustment posting now
We have a couple blogs related to Dynamics Online Payment Services SDK for Dynamics AX 2012 that can be referenced:
AX for Retail: A Better Sample for EFT plug-in (Credit Card processing)
AX for Retail 2012: EFT (Credit Card Processing) Sample is Now Available
Dynamics 365 for Operations offers a MasterCard and VeriFone out of the box redistributed solution as part of Dynamics 365.
-Card-Not-Present solution with Token and MasterCard Hosted Payment Page.
-Supports Accounts Receivable and Call Center sales orders, E-Commerce sales orders, POS customer orders for 13 markets (Australia, Canada, Denmark, France, Germany, Iceland, Ireland, Mexico, Netherlands, New Zealand, South Africa, United Kingdom, and United States)
-Mastercard owns IP and is responsible for servicing and Microsoft re-distribute
-Signup URL https://www.simplify.com/microsoft
-Card-Not-Present and Card-Present solution with E2E encryption, token and Hosted Payment Page.
-Supports Accounts Receivable and Call Center sales orders, E-Commerce sales orders, and POS customer orders, POS Cash & Carry for US Market with MX 925, 915 and e355.
-Verifone owns IP and is responsible for servicing and Microsoft re-distribute
-Signup URL: http://lp.verifone.com/us/microsoft-dynamics/
Dynamics 365 for Operations Payment SDK sample connector is included in the Retail SDK folder:
RetailsSdk\Payments
RetailSdk\Externals
This is for generating a deployable package for the payment connector.
Dynamics 365 for Operations Payment related documentation:
http://download.microsoft.com/download/4/D/7/4D7C6B05-0C23-4C6C-BA13-AB62ED08AA61/The Guide to Implementing Payment Connector and Payment Device.docx
http://ax.help.dynamics.com/en/wiki/create-a-windows-installer-for-a-payment-connector
https://ax.help.dynamics.com/en/wiki/deploy-payment-connector/
Scenario:
You may find sometimes, the retail return transactions (from EPOS or MPOS) cannot get the same cost price of the original sales. Normally, this is caused by the return statement is post in the same statement with the original sales.
Let’s use the below example.
We have an item ‘Test’ which is using moving average item model group. The default cost price maintained in the item master data is $20. The store tender Alex sell the item from POS on Dec 26 2016. Later on the same day, customer decide to return the item due to certain reasons. So, Alex make the return through POS later that day.
Then, at the end of the day posting, the sales and return transactions are post in the same statement. Let’s assume the cost of the item at the stamen posting time is $22.00. Now if you check the sales transactions, it uses $22.00 as the cost price, while the return price uses the default cost price $20.00.
Note: If there is no default cost price defined in item master data, the return cost price will be zero.
Reason:
Return transaction cannot be matched with the original sales transaction.
Resolution:
By resolving the scenario, you can install hotfix KB 3139018. After installing the hotfix, both sales and return transactions will use the running cost. Thus, if the sales and return transactions are post in one statement, they will get the same cost price.
Note: This hotfix only works for moving average not for other item model types.
