DAC | Divide-and-Conquer Parallel Pattern Implementation | Architecture library

So, the best solution to this we found so far is to update the Graph in the row persisted.

Besides writing code to enable the field in RowSelected event, it is also important to add the field in Closed state in the Workflow.

However, if this is also not working deleting contents of CstDesigner of project does the job.

I would check your customization page definition, my guess is that you created the wrong kind of control to present your date field. Go into 'Customization Project Editor', click on your screen under the 'Screens' header, Click on your grid, click on the 'Add Data Fields' column on the right. Check for your 'Valid To' field and make sure it's not listed with a Selector Control or something other than DateTimeEdit. If it is, you can delete, change the control, and re-add.

Unfortunately, implementing a complex and hierarchical authorization model like this within a database is... not simple. Given the requirements presented (similar roles across multiple resource types), and the need for “inheritance” of those roles, I’ve outlined a possible model to store the roles:

Each row in the table would contain a user, their role, and one of the {survey, collection, series} to which the role applies. This would allow your application to easily lookup the role (which are standardized) for the given resource you are checking. This is a pattern similar to Generic Foreign Key in Django. However, it still leaves one key problem: the heirarchy.

One option would be define a function in your code that knows which roles to lookup for each level of your heirarchy, so if it is given a survey, it looks up the roles for the user in all levels (survey, collection, series) and returns the role with the greatest access to check against. Otherwise, you'd likely need to make use of a series of joins to select all the roles for the user and the incoming resource, which could become very slow as your tables grow larger. This also only works if your roles remain the same at each level; otherwise, you'll find yourself quickly having to compare different enumerations of roles.

Hierarchical questions of these sorts appear in permissions checking often, and your unease is a recognition of that fact that its tough to map them in traditional relational databases: permission relationships are, at their core, a graph, and relational databases were not designed for easy traversal of graphs.

As a result of this complexity, there are services (this one is mine) that abstract away this complexity for you, so you can define your roles and relationships and not have to worry about the traversals. As a demonstration, I took the requirements you listed above and wrote an example in our playground, which might help you visualize and test these relationships.

I am not 100% certain, but I think this is about the ID's in the ASPX rather than the database data. For example:

Notice ID="PXLayoutRule1" in that sample. If this "ID" value of any entry in the ASPX is duplicated anywhere in the screen as an ID of another entry, you will get an error.

I had similar issues in an earlier version, especially when I would try to customize a screen and have the customization screen interface crash on me in the middle of it. I'd try deleting the screen, but I'd get orphaned files in the CstDesigner and CstPublished folder, which would really compound my issues.

Hopefully, you know how to look through your ASPX file and the Customization Project XML to check all the ID's. If you do know how to walk through all that, just add something to all of your ID values, like an X at the end. (i.e. PXLayoutRule1X) If not, gaining that familiarity is a worthy side-objective as you continue on.

If your issue is the same as I had in the past and you cannot simply find and edit the duplicate ID in the ASPX file or Project XML, here are some steps to take AFTER you backup your project and the affected folders noted in these steps. And, of course, this also assumes you are working in a development copy of your instance. (I often clone my main DEV instance to my laptop to test things like this if I am unsure so that my DEV instance stays unaffected. It just takes extra time you may or may not have.)

1. Delete the screen from your customization project.
2. Locate the folder CstDesigner and CstPublished under your instance's root folder (i.e. AcumticaDEV, Sandbox, etc. where your site exists)
3. Go into the Pages_XX folder (where XX is the 2 character code for your 1st 2 letters of the screen ID)
4. Delete the screen file(s) from there, if you find them.
5. If this is a custom screen, go into the Pages folder which is located in the same root folder of your instance as those folders in step 2 and repeat steps 3 and 4 in that folder.
6. Check for any reference to your screen in the Project XML from the file menu in the Customization Project screen and remove those sections if they exist. (This tends to relate more for customizing an existing screen.)
7. Publish your project.
8. Start over on your page and see if you still get the error.

Again, be sure to get a backup before taking these steps so that you can easily put it back if that does not resolve your problem.

Not sure what changed, but uninstalling and reinstalling the SQLServer module and then adding import-module sqlserver at the top of the script seems to have fixed it

Finally I got to the root cause of the issue,

Copy paste works as expected for PXRevisionableGraph as it should, the issue was with the Attributes used with the DAC fields. IN my case we have used PXFromula attribute that was used to calculate the SUM of the Child rows. Once that is commented everything start working as expected. we added the events for calculating the SUM instead of PXFormula now.

The document is in released status. There are mechanisms to prevent field editing when a document is in a closed state. It is not recommended to enable fields in this situation.

To enable the fields you need to revert the mechanism blocking editing. It is often the AllowUpdate property of the data view that is used to do so but it can also be automation steps or the workflow system.

When re-enabling AllowUpdate, you need to disable and re-enable the fields:

Because this error occurs sporadically, it took some time to verify a solution. But I found that using try: except: allowed the problem to resolved with the following code modification.