Blank Kinetic Layer after moving it

Kinetic ERP
1

I’ve got a dashboard with layer that was signed off from a Dev environment and moved via Solution to another environment as usual for further testing, but in this case the entire dashboard and layer is blank in the new environment. Opening them in Application Studio shows no components at all. No dataview, no pages, no events, no controls. Nothing.

Importing the layers again and overwriting doesn’t help.

Has anyone seen this happen before, and was there a fix for it? Just before I accept that I need to start again and recreate it …

2 Likes
2

I would try publishing the layer in the Dev environment and repacking it before moving it. It may not be saving the changes even if it was committed.

I’ve only done this once and I use exporting instead of solutions.

3

Yep multiple times. Which version? You can try exporting and importing directly in app studio. Delete the corrupt layer before importing again.

4

Thanks, both.

I’ve tried every way I can think of, solutions and export/import and deleting, and it’s still not cooperating. It looks as though there’s something fundamental wrong and rebuilding will be the way to go, unfortunately. It’s complaining that the base dashboard “is not accessible”, and somehow that itself is also both blank and has imported with a system flag so I can’t update it. All very odd.

5

Yep, been there, many times. You can get a data fix from support to at least delete it.

6

If I need support then I’ve already lost more time than rebuilding it …

I do miss the robustness of the older developer systems, I must say.

2 Likes
7

A kinetic layer is not a real layer until you have rebuilt it at least 3 times
Sad Sob GIF by MOODMAN

3 Likes
8

If you’re on prem and comfortable with it, pull out the published XXXDef.Content from Dev and put it in Live and see if that brings it back to life.
You could also do a query to see if that’s even there in Live first.

***Disclaimer
Play with SQL at your own risk, blah, blah, blah.
Take a backup first or whatever to cover your ass.
Totally don’t YOLO things like I do.
(I should write these disclaimers professionally)

3 Likes
9

I would if it was on-prem, and have taken a look at XXXDef in a BAQ in any case, just to see if there are any clues. But this one is cloud so better left alone, I think.

One of the things I’ve learned is that if something is going wrong for no reason then in the long term it can be wiser to rebuild anyway, because it can keep creeping back. It’s tiring and annoying, but never takes as long the second time.

10

I’d laugh, but it’s true.

11

If the dashboard is showing as system in the new environment then that means that not all the records needed for the dashboard were imported.

For a custom app / dashboard in Kinetic there are 7 (off the top of my head) records needed that make up the dashboard.

How did you move the Dbd the first time? Did you use solution workbench and if so did you use the KineticApp element or the user defined > GenXData service? If the later then you need to make sure you select all the records for the Dbd. In newer versions > 24.1 the KineticApp element is the way to go.

12

And another option you may have heard me mention one or two (million) times: let’s empower Solution Workbench with source control!

Make the software more friendly for DevOps | ERP-I-139

1 Like
13

Netflix Shrug GIF by The Animal Crackers Movie

1 Like
14

Add Julie Andrews GIF by The Rodgers & Hammerstein Organization

south park beat a dead horse GIF

15

Channel 9 Reaction GIF by The Block

Parks And Recreation Gimme GIF

1 Like
16

It was a solution with KineticApp, the same as all the other solutions which worked …

I am noticing, though, that solution workbench is leaving a lot of things undone in the newest cloud versions. I am growing a checklist of things to go in and check manually. It seems to have choked on one component of this, presumably one I can’t see.