To debug without setting up a startup project and startup object in D365 fotr operations. Follow these steps:
You can execute your process now from the client and execution will be stopped at your breakpoints.
Recently faced a problem where my breakpoints weren’t loading for objects in the AOT that were not in my solution and therefore I could not debug.
Solution: In order to load symbols for objects that have not been included in your solution you have to uncheck the following check box.
Dynamincs365>Options>Dynamics 365>Debugging
Load symbols only for items in the solution
To know more about how to debug in D365 visit: Debug X++
To recall a workflow through code you can use the cancelworkflow method in workflow class. It takes the correlationId and a comment as parameters and gets the job done for you. Example
workflow::cancelworkflow(CorrelationId, “Cancelling this workflow”)
Now you are probably thinking How do I find my workflows CorrelationId. You can do that by querying WorkflowTrackingStatusTable sorting it with time and instance number and joining it with SysWorkflowtable against the correlationId field and in the contextId you pass the RecId of your record for example PO RecId.
When editing a PO line for procurement category you receive Field ‘Company’ and ‘Lot ID’ must be filled in” error. This usually happens when you have brought in the PO line through some form of integration either AIF, excel plugin etc.
This error has also been seen on salesLine and there is a hotfix(KB 2756645) for when it happens on salesline.
Reason:
There is no record in PurchLineForeignTradeCategory table related to PO line added.
Solution:
Create a record against the PO line causing this error in the PurchLineFroeignTradeCategory table in your integration and you will see the error disappear.
In X++ we have the below methods for fetching data after any changes are made, below is the short description of what they are and when to use each one.
Refresh() refreshes the user view with whats stored in the caches. This does not touch the DB.
Use this after any form change has been made through code.
ReRead() fetches only the current record from database and does not re read the complete datasource.
Use this when you need to update only the current record after modifying any value.
ReSearch() will execute the same query again and fetch the results from the database.
Use this if you need to get the current most data from database.
ExecuteQuery() will run the query again just like research does but it will also take any query changes into account.
Use this is you have modified the query on run-time and need the updated results according to the new query.
To connect to an external database with X++ you can use Open Database Connection (ODBC) protocol through the OdbcConnection class among other ways. This approaches requires you to setup us a Data Source Name(DSN) on your server machine with the required access. Below is the code sample for how you can achieve this.To read more about this visit MSDN.
// X++, Main method in a class.
static public void Main(Args _args)
{
LoginProperty loginProperty;
OdbcConnection odbcConnection;
Statement statement;
ResultSet resultSet;
str sql, criteria;
SqlStatementExecutePermission perm;
;
// Set the information on the ODBC.
loginProperty = new LoginProperty();
loginProperty.setDSN("dsnName");
loginProperty.setDatabase("databaseName");
//Create a connection to external database.
odbcConnection = new OdbcConnection(loginProperty);
if (odbcConnection)
{
sql = "SELECT * FROM MYTABLE WHERE FIELD = "
+ criteria
+ " ORDER BY FIELD1, FIELD2 ASC ;";
//Assert permission for executing the sql string.
perm = new SqlStatementExecutePermission(sql);
perm.assert();
//Prepare the sql statement.
statement = odbcConnection.createStatement();
resultSet = statement.executeQuery(sql);
//Cause the sql statement to run,
//then loop through each row in the result.
while (resultSet.next())
{
//It is not possible to get field 3 and then 1.
//Always get fields in numerical order, such as 1 then 2 the 3 etc.
print resultSet.getString(1);
print resultSet.getString(3);
}
//Close the connection.
resultSet.close();
statement.close();
}
else
{
error("Failed to log on to the database through ODBC.");
}
}
Here is how you can connect to an external database using X++ SqlClient class. This is among the few others approaches you can connect to an external database.
public System.Data.SqlClient.SqlConnection getConnection()
{
str connectionString;System.Exception exception;
System.Data.SqlClient.SqlConnection connection;connectionString = “Persist Security Info=False;User ID=UserID;Pwd=Password;Initial Catalog=DatabaseName;Data Source=localhost;”;
try
{
connection = new System.Data.SqlClient.SqlConnection(connectionString);
connection.Open();return connection;
}
catch (Exception::Error)
{
error(“An exception has occurred.”);
}
catch (Exception::CLRError)
{
error(“A CLR exception has occurred.”);exception = CLRInterop::getLastException();
if (exception != null)
{
info(exception.ToString());
}
}return null;
}
To run a query after a successful connection, use this code:
System.Data.SqlClient.SqlConnection conn;
System.Data.SqlClient.SqlCommand cmd;
System.Data.SqlClient.SqlDataAdapter da;
System.Data.SqlClient.SqlDataReader dr;
System.Exception netExcepn;str sql, attributeName, attributeValue;
str 30 materialCode;mzkConnectToDB = new MzkConnectToDB();
conn = mzkConnectToMSDgen.getConnection();sql = strFmt(“select * from tablename;”);
cmd = new System.Data.SqlClient.SqlCommand(sql,conn);dr = cmd.ExecuteReader();
while(dr.Read())
{
try
{
materialCode = dr.get_Item(‘material_id’);}
}
catch(Exception::Error)
{
error(“@SYS85688”);
}
}//Close the connection.
dr.Close();
conn.Close();
}
While creating a certificate with the MakeCert utility you might face this Error: Save encoded certificate to store failed => 0x5 (5) as I did, dont be worried its not about your command the solution to this is to simply start your command prompt or powershell as an administrator and then run the command; the certificate will be created successfully.
Us ISVs( Independent Software Vendors) want to make our own customized Ax solutions to run on predefined licenses so we can better monetize our solutions, well thanks to Microsoft we now have an ISV licensing feature to do this and do not need to create our own licensing mechanisms. The ISV licensing feature includes the following key capabilities:
You can read more about ISV licensing here. In this post I will be showing you step by step how you can create your own ISV licence against a model. Before you can create a license you also need to have certificates in order to sign that license so here are the complete steps from start to end:
C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin
Once you have implemented the code with the above approach, you can then generate a license for your solution as explained below:
Hope this post was helpful, for any questions feel free to leave a comment. Here are some good resources that helped me understand ISV licensing.
UPDATED: To overcome the “Certificate associated with license XXX is not a trusted certificate.” Error while importing license file the complete steps for creating our own certificate have been update, please find the updates in blue text.
Developers often ask me what the difference is between the three different menu item types shown in AOT and when should you use them as it appears that all menu items inside the three ‘folders’ I would say have the same set of properties and support the same object types. So what is the difference? The answer is that there is no difference, the difference is a conceptual one rather than a functional or a technical one.
1. Display Menu item
This folder is used to contain menu items that reference runnable objects which are primarily for presenting data to the user such as forms and dialog’s.
2. Output Menu item
An output menu item should have the soul purpose to print a result, mostly used for referencing classes.
3. Action Menu item
As the name says it, you should create a menu item under this folder if your runnable object has an action to perform, for example creating or updating data.
So choosing between these three is on the developers sole discretion and I hope now you’ll be able to make a better choice for your scenario. A basic rule of thumb is:
Display – for Form
Output – for Report
Action – for classes.
For more information visit : Msdn Menu Items Best Practices [AX 2012]
Mohsin Khalid 