I'm on a dynamics NAV 2013 training (self study) with a perpetual license. I use a suitable database for a particular business (with some specific functionnalities)
When i want to change "Due Date" in "Service Order module>Service Jobs" i obtain this error message :
In The current Company the date you've entered is outside the allowed interval (this is determined by the filter '??11|b??12*|??01*|??02*', which is defined by the license file).*
when i choose a date before 03/01/2016 (March) i got this error message :
Service Job Due Date cannot be in the past
I need your help to find how can i change this filter (in the license file) in order to change this field easily.
thanks in advance for your help
Just as comments from Mak Sim and azatoth This isn't NAV standard. This is custom code. Debug the code and you can see the problem.
This is standard behaviour; NAV is effectively in 'Demo-Mode' at this point.
It seems to happen either when the license on your NAV Server expires, or when you have installed a new license, but not restarted the service.
In either case, the resolution is to install a valid license from the NAV Development Environment, then restart the NAV service on the middle-tier server.
Related
I have no idea how to debug Dynamics 365 Business Central ERP Application in an on-premises server.
Can you guys help me out?
Not to just link documentation, but the best place to get started is the MSDN documentation on Business Central debugging. If you're trying to debug an existing session, you'll want to use Attach and Debug Next.
Both debugging scenarios will require the source code of either the app you're debugging, or the base app that was used to deploy it. Otherwise, view last error (in the help menu) is the only use facing debugging option.
If you have any specific questions, I can point you in the right direction.
we are using Microsoft Sync Framework 2.1 in various customer projects for file and database sync. Extended Support will end in 2021.
So my questions are:
What is Microsofts strategy for the sync framework? Is it going to be open source, so we can change if needed ourselves? Is there a successor product that we should / can migrate to?
Is MSSF supported on Windows 10 and Server 2016?
Not sure if my answer really helps, but lets see: Microsoft announced the official release of the "Azure SQL Data Sync" on June 18 2018. It is not truly a successor of the original framework, but it is basically all you get. Other "non cloud" frameworks have also started to fade away, since Microsoft treats server/desktop/on-premise only as an extension to the cloud. As the name indicates, it is targeting Azure and it is not for file sync, either.
I have seen your question also in the "old" Microsoft social network (social.msdn.microsoft.com/Forums/en-US/home). In there they point to this framework in questions related to the original "Sync Framework" since something like 2012 (this was the oldest question I could associate with both frameworks).
We have submitted a UWP app, built using the Windows 8.1 SDK, to the Windows Store, published with the 'Private Audience' option. We observe that LoadListingInformationAsync (in the CurrentApp class) throws a 0x80190194 Not found (404) exception.
This happens regardless whether we run the project in Visual Studio or whether we install the Store version. The In-App products have been added, published and are all marked with 'In The Store'. We have checked that all the identifiers/names listed under 'App management/Identity details' match those in the manifest. We have checked that the In-App-Code works as expected with the CurrentAppSimulator. We have also used a network traffic monitor to check for network errors and haven't found any.
We have posted the same issue in the windows forum where it was suggested by a Microsoft employee to simply wait a couple of days. It is now two weeks since our in-app-products were published in the dashboard. This problem is blocking us completely and we definitely need help in fixing this issue.
Therefore we would very much appreciate if someone at Microsoft could find out why the in-apps published in the dashboard apparently haven't been installed correctly in the store and thus aren't visible from our application.
Here is our Package SID:
S-1-15-2-2762217728-2497590674-2702625719-1901796822-1169495103-2187450542-4267134542
We have upgraded Sitecore to 7.1, but we are experiencing a problem with publishing.
We create a new item in the master database in English, then we publish this item, switch to the web database to check if it's there, which it is, however... The item does not have a version! Therefore the item is not displaying on the website.
Any ideas as to what could be causing this?
Thanks.
I was having the same issue with Sitecore 8+ where i was able to add language specific content but couldn't publish it. Figured out how to resolve it
1) First Language needs to be registered in \sitecore\system\languages by defining the language to be use.
2) Publish these language items first before publishing content else the behavior will be the same.
3) After publishing languages, then publish the content. In the publish window you will see the language under "Publishing language" section and select the language to publish the content.
Make sure that parent items have a version as well and are also in final state if they are part of a workflow.
I had problems with publishing because I didn't have a language version in one of my parents. In my case it was a parent folder under the content node.
Hope it helps.
Al
Please try republishing your entire site. In some cases, a part of the tree hierarchy might be missing in the Web DB, due to which, publishing the child nodes wouldnt work. Republishing the site can eliminate this chance.
This has been resolved.
It turns out that the SQL server did not have enough space for a full publish. A full publish had been attempted and failed due to the lack of space on the SQL server. subsequently this had corrupted the database.
We had to restore an earlier version of the database and ensure the SQL server had plenty of space for the full publish to finish.
I ran into this issue earlier with my Sitecore 7.2 upgrade. The key here is to ensure the items, templates and layouts (associated with the item) all has appropriate language+versions in master db. In my case, we were also using Partial Language fallback and needed to make that was working proper as well.
Once you identify the item (with missing versions), add them and republish the whole item. For few template types I noticed Sitecore was still not publishing properly. Ex: Items based off Sublayout Folder template. The fix was easy in this case as I changed the template type to Folder and republished.
Also switch to web database in sitecore client and ensure you are able to preview the item (from web db)
Hope this helps.
I have a requirement to allow users of the web site to see the current publish version of the item (which has passed through workflow) + the previous versions + the version scheduled to publish in future.
So when the use visit the content item on the web site they will be presented with tabs to: previous , current and future version of the item.
I have seen some articles how to intercept publishing pipeline but still cannot evaluate if this scenario is possible.
There is no native way to allow multiple versions to be published live at a given time. This comes down to how the publishing process works for Sitecore. At a high-level, let me explain:
The authoring environment which uses the master database contains 0-n versions of each item. When a user decides to publish a piece of content, only the latest version marked as "final" will be published to the publishing target database, e.g. usually the web database. The publishing target database (e.g. web) will always only have ONE VERSION of a given item, unlike the master database.
Let me say that again:
The front-end public-facing website's database
only has ONE VERSION of a given content item at any time.
Since you indicated the front-end of the site needs to show three versions coming from:
Previous
Current
Future
This means that the pure requirement of showing a "future" version to be published means your site would not use a typical master-to-web publishing model and would instead need to run in "live mode" which runs from the master database. As I said, you would not even publish at all and would render content as you edit/save it.
So, for this reason, you'd need to code your front-end presentation component(s) which generate the tabs to query the item and get the current version, the previous version (assuming it was "final"), and a previous version (assuming its "final").