Is there a way to make a Generic Inquiry(GI) able to see soft deleted data on Acumatica? For example I'm working on a GI that looks at contact that's been deleted. It is doing a Soft delete the column name is [Contact.DeletedDatabaseRecord]. I'm working on Acumatica 2018 R2 verison number 18.206.0011.
This feature is available for reports but not for generic inquiry.
A feature request exists for allowing selective filtering of the records marked as deleted in generic inquiry:
https://feedback.acumatica.com/ideas/ACU-I-1728
It was created on 28 September 2018 and already has garnered five votes so there's a reasonable chance it gets implemented in future versions:
Related
I'm trying to get the active view of my family's document but it returns null. In Revit 2019, it would always return a value however I've recently switched to Revit 2020 and it seems to be giving me an issue.
Has anyone else run into this yet and come across a solution?
I've stumbled across this post but its recommendation is to use a filtered element collector which I am not a fan of. I'm having issues passing it to other classes. Revit 2019 seemed so simple.
Note: this also persists in Revit 2021
Here's a picture of my debug showing its null
and then here's a picture of my Snoop for the family document after it is open and activated showing it has a value.
The reason behind this is that you are currently working on a project document, which means the project document is open and 1 of its view is showing in Revit graphical view, not the family document. Therefore, the View from the family document is not showing - A.K.A no active view for the family document.
The solution you are looking for is explained in this post:
switch view or document by showing elements
In short, you create an UIDocument from family document, then use the newly created UIDocument to show the family document via:
UIDocument.ShowElements()
After that, you have an active view for your family document.
I am testing an upgrade from Acumatica Version 6.10.0755 to 2018 R2 in a development instance on my local Windows 7 computer. I have completed the upgrade process, and now when attempting to load the AR Aged Period Sensitive report (AR630500), the web interface returns a PXException:
Cannot resolve the table name: [PX.Objects.GL.FinPeriod]
I have examined the report in the report designer, and the Build Schema window loads the FinPeriod table with no problems. I compared it to the same report in 6.10.0755 and it appears that the report is the same.
The only lead that I have seen is that in the website's code repository, the location of the DAC definition, FinPeriod.cs, has moved; in 6.10.0755 it is located in \PX.Objects\GL\DAC. But in 2018 R2 the FinPeriod.cs file is located in a new subfolder, \PX.Objects\GL\DAC\FinPeriods.
I have found no reference to this change in the structure of the GL module anywhere in any of the release notes, and I am at a loss as to what possibly went wrong.
First few lines of the stack trace:
[PXException: Cannot resolve the table name: [PX.Objects.GL.FinPeriod]]
PX.Api.Soap.Screen.ReportNameResolver.ResolveTable(ReportTable t)
PX.Data.Reports.SoapNavigator.a(Object A_0, String& A_1)
PX.Data.Reports.SoapNavigator.GetFieldSchema(Object field)
PX.Web.UI.PXReportViewer.r()
...
I found the answer; it turned out the report was a customized version of the stock report that had been created (but not documented) before I started working on the project. The upgrade process kept the customized report as-is with the old table references. To correct this, I simply used the File>Build Schema menu option in the Report Designer, removed the old FinPeriod table, and added the MasterFinPeriod table, then used the Refactor button, which automatically mapped the relevant fields from the new table.
According to Acumatica release notes table FinPeriod was renamed in 2018 R2. Right now I can't provide you the name of a new table. You need to find what is replacement for it by going through different release notes.
I have removed sharing from a record in CRM manually. It is not shared via cascading rule eather, but it remains in Principal Object Access table. As I can see, the script for controlling growth of POA, published by Microsoft, deletes only rows with object ids which er deleted from CRM, can't see logic which removes those unshared records.
Does anyone know if CRM contains logic for this at all? Has anyone had experience with deleting those rows despite of being unsupportet action?
Thanks in advance
I can't tell you very much about how the POA table is populated or cleaned up, but I can tell you how to delete it:
http://dotnetdust.blogspot.com/2014/01/lessons-learned-deleting-312-million.html
Sharing also present for some entities even you can't see it in UI. Implicit sharing is created during entities merge or for email activities when there are different users in to:, cc: fields, for workflow logs, process sessions, etc.
I wrote short article about it: http://tunnik.name/principalobjectaccess-table-clean-it-up-fast/
It has links to other articles which can help dig into that subject.
I designed a site in share point. There is a column called "Issue ID (linked to item)" in ALL Issues view. I am using this column to list and identify the items which are created by employees. It increases by 1 as a new issue is created. Unfortunately, I have to reset this ID to 1 because during the test period I created and deleted blank issues. Although they were deleted, the share point increasing Issue ID from the last deleted issue (89).
Is there an easy way to do this? how can I reset this auto number? I need to reset this counter as soon as possible without any risk...
Do you kindly help me? I would be glad if you explain it in detail.
Thank you,
If your Issues list wasn't heavily customized and nor referenced by GUID in any custom code, the simplest and most supported option would be to recreate it with the same name after deletion as a customized template you could have saved without contents from list settings page before deleting or as a standard Issues list.
On of our SharePoint users informed me today about a strange behavior of a discussion board on one of his sites.
Normally the standard "subject" view of an discussion list has a field named "Last updated" showing the date and time of the last post within the corresponding thread. On the discussion board of our user this field is never set to the date/time of the last post but stays on the date/time when the thread was started.
The site on which the discussion board is located was created from a custom web site template which includes the empty discussion board.
To narrow this problem I created a second discussion board on the same site, with the result that it sets the Last updated field correctly.
Any suggestions why the Last updated field doesn't update any more?
Has the view been modified to use the creation date instead? I've had more than a few problems with people accidentally modifying the shared view of a list instead of the personal view...
We've experienced the same behavior. No solution, but the Last Modified field seems to do the same.